[v12.x backport] deps: V8: cherry-pick 0dfd9ea51241

[bcoe]

Original commit message:

[coverage] Fix coverage with default arguments
In the presence of default arguments, the body of the function gets
wrapped into another block. This caused our trailing-range-after-return
optimization to not apply, because the wrapper block had no source
range assigned. This CL correctly assignes a source range to that block,
which allows already present code to handle it correctly.
Note that this is not a real coverage bug; we've just been reporting
whitespace as uncovered. We're fixing it for consistency.
Originally reported on github.com/bcoe/c8/issues/66
Bug: v8:9952
Change-Id: Iab3905f558eb99126e0dad8072d03d0a312fdcd3
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1903430
Commit-Queue: Sigurd Schneider <sigurds@chromium.org>
Reviewed-by: Toon Verwaest <verwaest@chromium.org>
Reviewed-by: Jakob Gruber <jgruber@chromium.org>
Cr-Commit-Position: refs/heads/master@{#64836}

Refs: v8/v8@0dfd9ea

PR-URL: #30713
Reviewed-By: Michaël Zasso targos@protonmail.com
Reviewed-By: Colin Ihrig cjihrig@gmail.com
Reviewed-By: Jiawen Geng technicalcute@gmail.com
Reviewed-By: Rich Trott rtrott@gmail.com

Checklist

• make -j4 test (UNIX), or vcbuild test (Windows) passes
• tests and/or benchmarks are included
• documentation is changed or added
• commit message follows commit guidelines

[bcoe]

V8 tests: https://ci.nodejs.org/job/node-test-commit-v8-linux/2806/

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/28480/

[bcoe]

@targos I believe this should be ready to go.

[mhdawson]

LGTM, but @bcoe wondering why the change to code-coverage-block-async.js is not included?

[bcoe]

@mhdawson in the rebase, it seems like something in the nodejs:v12.x-staging branch, perhaps something else we backported, removes the code-coverage-block-async.js test file. I didn't think this was the end of the world, as we have coverage in code-coverage-block.js.

[MylesBorins]

landed in 02d7283