Revert of Reland: [Parse] ParseInfo owns the parsing Zone.

Revert of Reland: [Parse] ParseInfo owns the parsing Zone. (patchset #6 id:120001 of https://codereview.chromium.org/2632123006/ )

Reason for revert:
Makes the tree red. Maybe outdated compile tryjobs?

E.g.:
https://build.chromium.org/p/client.v8/builders/V8%20Linux%20-%20builder/builds/22988

Original issue's description:
> Reland: [Parse] ParseInfo owns the parsing Zone.
> 
> Moves ownership of the parsing Zone to ParseInfo with a shared_ptr. This is
> in preperation for enabling background compilation jobs for inner functions
> share the AST in the outer-function's parse zone memory (read-only), with the
> and zone being released when all compilation jobs have completed.
> 
> BUG=v8:5203, v8:5215
> 
> Review-Url: https://codereview.chromium.org/2632123006
> Cr-Commit-Position: refs/heads/master@{#42993}
> Committed: https://chromium.googlesource.com/v8/v8/+/14fb337200d5da09c77438ddd40bea935b1dc823

TBR=marja@chromium.org,mstarzinger@chromium.org,ahaas@chromium.org,verwaest@chromium.org,rmcilroy@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=v8:5203, v8:5215

[Michael Achenbach, 2017-02-07 13:03:19]

The CQ bit was checked by machenbach@chromium.org

[Michael Achenbach, 2017-02-07 13:03:20]

Created Revert of Reland: [Parse] ParseInfo owns the parsing Zone.

[commit-bot: I haz the power, 2017-02-07 13:03:23]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[Michael Achenbach, 2017-02-07 13:03:48]

The CQ bit was unchecked by machenbach@chromium.org

[Michael Achenbach, 2017-02-07 13:04:01]

Jochen was faster...

[marja, 2017-02-07 13:40:25]

Sounds like a bug if the CQ commits stuff because of some too old tryjobs!

[Michael Achenbach, 2017-02-07 13:47:00]

On 2017/02/07 13:40:25, marja wrote:
> Sounds like a bug if the CQ commits stuff because of some too old tryjobs!

No that's by design. Otherwise CQ would need to rerun all bots each time HEAD
changes. The current validity of a tryjobs is somewhere between 12 and 24 hours.
But even if we limit it to 1-2 hours (which we could) we might get CLs racing
with each other... Currently we get a breakage of that sort once every two
weeks...

[marja, 2017-02-07 13:47:58]

On 2017/02/07 13:47:00, Michael Achenbach wrote:
> On 2017/02/07 13:40:25, marja wrote:
> > Sounds like a bug if the CQ commits stuff because of some too old tryjobs!
> 
> No that's by design. Otherwise CQ would need to rerun all bots each time HEAD
> changes. The current validity of a tryjobs is somewhere between 12 and 24
hours.
> But even if we limit it to 1-2 hours (which we could) we might get CLs racing
> with each other... Currently we get a breakage of that sort once every two
> weeks...

Yep, I realized based on the comments in the CL that it's a real in-flight
conflict and thus not a bug.