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

Checklist

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

This addresses: bcoe/c8#66, bcoe/c8#151

[nodejs-github-bot]

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

[addaleax]

V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/2667/

[nodejs-github-bot]

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

[bcoe]

@addaleax it looks like the pertinent V8 tests (coverage-block-async, and coverage-block) have passed 👍 (it looks like unrelated V8 failures have been failing for all builds recently).

I would like to fast-track landing this patch, while I have some cycles today.

👍 or 👎

[bcoe]

Landed in 5961161

[targos]

Should this be backported to v12.x-staging? If yes please follow the guide and raise a backport PR, if not let me know or add the dont-land-on label.

[bcoe]

@targos ideally we'd backport this, sounds like I should go through that guide?