deps: cherry-pick dbfcc48 from upstream V8

[alexkozy]

Original commit message:

[inspector] added V8InspectorClient::resourceNameToUrl Some clients (see Node.js) use platform path as ScriptOrigin. Reporting platform path in protocol makes using protocol much harder. This CL introduced V8InspectorClient::resourceNameToUrl method that is called for any reported using protocol url. V8Inspector uses url internally as well so protocol client may generate pattern for blackboxing with file urls only and does not need to build complicated regexp that covers files urls and platform paths on different platforms. [email protected][email protected] Bug: none Cq-Include-Trybots: luci.chromium.try:linux_chromium_headless_rel;luci.chromium.try:linux_chromium_rel_ng;master.tryserver.blink:linux_trusty_blink_rel Change-Id: Iff302e7441df922fa5d689fe510f5a9bfd470b9b Reviewed-on: https://chromium-review.googlesource.com/1164624 Commit-Queue: Aleksey Kozyatinskiy <[email protected]> Reviewed-by: Alexei Filippov <[email protected]> Cr-Commit-Position: refs/heads/master@{#55029} 

Refs: v8/v8@dbfcc48
Needed for #22223

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

[nodejs-github-bot]

@ak239 build started: https://ci.nodejs.org/blue/organizations/jenkins/node-test-pull-request-lite-pipeline/detail/node-test-pull-request-lite-pipeline/507/pipeline

[alexkozy]

By accident I broke my previous PR: #22224
So I created new one. Please take a look!

[Trott]

@nodejs/v8

[TimothyGu]

This LGTM by itself, but I'd prefer landing this with the actual Node.js resourceNameToUrl implementation.

[alexkozy]

@TimothyGu please take another look.
I pushed second commit that contains resourceNameToUrl implementation.

[alexkozy]

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

[alexkozy]

@TimothyGu I addressed your comments and added one more test. Please take another look.
CI: https://ci.nodejs.org/job/node-test-pull-request/16878/

[TimothyGu]

Newly added code LGTM. Some logistical comments.

[TimothyGu]

I'm a bit reluctant to touch into the internals in this way. Could something like this work?

URL url("file:///");

This will also need a cctest (see https://github.com/nodejs/node/blob/master/test/cctest/test_url.cc).

Finally could you split the changes to node_url into a separate commit?

[alexkozy]

Addressed comments and started another CI: https://ci.nodejs.org/job/node-test-pull-request/16880/

[TimothyGu]

Looks good to me.

[TimothyGu]

Hmm, jumped the gun there. Left a few more comments.

Dismiss stale review

[alexkozy]

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

[alexkozy]

Failure on Windows bot looks unrelated. @TimothyGu could you take another look?

[BridgeAR]

This needs a rebase.

[BridgeAR]

@nodejs/v8-update PTAL. This needs some LGs

[TimothyGu]

LGTM if tests pass.

[alexkozy]

Rebased and started CI: https://ci.nodejs.org/job/node-test-pull-request/17120/

[alexkozy]

rebased and restarted CI again since I believe that failure is unrelated: https://ci.nodejs.org/job/node-test-pull-request/17126/

[alexkozy]

Another try: https://ci.nodejs.org/job/node-test-pull-request/17151/

[alexkozy]

Windows bot looks disabled on CI, based on previous CI all related tests passed, I am not sure, should I wait until windows is fixed on CI or can I land it as is?