[v10.x] deps: cherry-pick d9fbfeb from upstream V8

[kjin]

Original commit message:

inspector: return [[StableObjectId]] as internal property

This property might be useful for fast '===' check.

[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: Iabc3555ce1ec2c14cf0ccd40b7d964ae144e7352
Reviewed-on: https://chromium-review.googlesource.com/1226411
Reviewed-by: Dmitry Gozman <[email protected]>
Reviewed-by: Yang Guo <[email protected]>
Reviewed-by: Jakob Gruber <[email protected]>
Commit-Queue: Aleksey Kozyatinskiy <[email protected]>
Cr-Commit-Position: refs/heads/master@{#56095}

See: #23886

Checklist

• make -j4 test (UNIX), or vcbuild test (Windows) passes
• commit message follows commit guidelines

[ofrobots]

CI: https://ci.nodejs.org/job/node-test-pull-request/20040/
V8-CI: https://ci.nodejs.org/view/All/job/node-test-commit-v8-linux/1996/

[kjin]

@ofrobots Seems like the CI failure is an unrelated flake: https://ci.nodejs.org/job/node-test-binary-windows/22973/COMPILED_BY=vs2017,RUNNER=win2016,RUN_SUBSET=0/

I've rebased to resolve conflicts in common.gypi.

[ofrobots]

The CI looks good to me. @nodejs/backporters this is ready to land.

[kjin]

@nodejs/backporters -- could we land this please? Thanks!

[ofrobots]

@nodejs/release @nodejs/backporters does the policy that only the backport team should be landing fixes on staging branches still make sense? Perhaps that is unnecessary burden on the team, and we should open this ability up to a broader list of collaborators to ensure things don't get stuck. Similarly: #25242.

[richardlau]

@nodejs/release @nodejs/backporters does the policy that only the backport team should be landing fixes on staging branches still make sense? Perhaps that is unnecessary burden on the team, and we should open this ability up to a broader list of collaborators to ensure things don't get stuck. Similarly: #25242.

Discussion over in nodejs/Release#388.

[BethGriggs]

Could we get a review from @nodejs/v8?, then this should land ready for v10.15.2

[ofrobots]

LGTM.

There were also LGTMs on #23886.
EDIT: launched a new CI: https://ci.nodejs.org/job/node-test-pull-request/20566/

[kjin]

Force-pushed to edit the commit message once again, seems like quoted commits need to be spaced 4 whitespaces instead of two.

[BethGriggs]

Landed on v10.x-staging in c9a3e40