Revert of [inspector] use creation stack trace as parent for async call chains

Revert of [inspector] use creation stack trace as parent for async call chains (patchset #2 id:20001 of https://codereview.chromium.org/2868493002/ )

Reason for revert:
CHECK is too strict.

Original issue's description:
> [inspector] use creation stack trace as parent for async call chains
> 
> Creation stack trace points to the place where callback was actually chained, scheduled points where parent promise was resolved.
> For async tasks without creation stack (e.g. setTimeout) we continue to use scheduled as creation since usually they are the same.
> 
> BUG=v8:6189
> R=dgozman@chromium.org
> 
> Review-Url: https://codereview.chromium.org/2868493002
> Cr-Commit-Position: refs/heads/master@{#45198}
> Committed: https://chromium.googlesource.com/v8/v8/+/e118462f18a862df81a04486e13dd62997cbfc5a

TBR=dgozman@chromium.org,alexclarke@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=v8:6189
Review-Url: https://codereview.chromium.org/2868423004
Cr-Commit-Position: refs/heads/master@{#45242}
Committed: https://chromium.googlesource.com/v8/v8/+/fe0d5c7ca80181d7a581de9cbcdc26a6b2a40b7a

[kozy, 2017-05-10 20:43:17]

The CQ bit was checked by kozyatinskiy@chromium.org

[kozy, 2017-05-10 20:43:19]

Created Revert of [inspector] use creation stack trace as parent for async call
chains

[commit-bot: I haz the power, 2017-05-10 20:43:21]

CQ is trying da patch.

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

[commit-bot: I haz the power, 2017-05-10 21:24:39]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1494448997894120, "parent_rev":
"e2890c19a70376686f025119082cfad6676a2f7b", "commit_rev":
"fe0d5c7ca80181d7a581de9cbcdc26a6b2a40b7a"}

[commit-bot: I haz the power, 2017-05-10 21:24:46]

Description was changed from

==========
Revert of [inspector] use creation stack trace as parent for async call chains
(patchset #2 id:20001 of https://codereview.chromium.org/2868493002/ )

Reason for revert:
CHECK is too strict.

Original issue's description:
> [inspector] use creation stack trace as parent for async call chains
> 
> Creation stack trace points to the place where callback was actually chained,
scheduled points where parent promise was resolved.
> For async tasks without creation stack (e.g. setTimeout) we continue to use
scheduled as creation since usually they are the same.
> 
> BUG=v8:6189
> R=dgozman@chromium.org
> 
> Review-Url: https://codereview.chromium.org/2868493002
> Cr-Commit-Position: refs/heads/master@{#45198}
> Committed:
https://chromium.googlesource.com/v8/v8/+/e118462f18a862df81a04486e13dd62997c...

TBR=dgozman@chromium.org,alexclarke@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=v8:6189
==========

to

==========
Revert of [inspector] use creation stack trace as parent for async call chains
(patchset #2 id:20001 of https://codereview.chromium.org/2868493002/ )

Reason for revert:
CHECK is too strict.

Original issue's description:
> [inspector] use creation stack trace as parent for async call chains
> 
> Creation stack trace points to the place where callback was actually chained,
scheduled points where parent promise was resolved.
> For async tasks without creation stack (e.g. setTimeout) we continue to use
scheduled as creation since usually they are the same.
> 
> BUG=v8:6189
> R=dgozman@chromium.org
> 
> Review-Url: https://codereview.chromium.org/2868493002
> Cr-Commit-Position: refs/heads/master@{#45198}
> Committed:
https://chromium.googlesource.com/v8/v8/+/e118462f18a862df81a04486e13dd62997c...

TBR=dgozman@chromium.org,alexclarke@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=v8:6189

Review-Url: https://codereview.chromium.org/2868423004
Cr-Commit-Position: refs/heads/master@{#45242}
Committed:
https://chromium.googlesource.com/v8/v8/+/fe0d5c7ca80181d7a581de9cbcdc26a6b2a...
==========

[commit-bot: I haz the power, 2017-05-10 21:24:46]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/v8/v8/+/fe0d5c7ca80181d7a581de9cbcdc26a6b2a...