deps: V8: respect interceptors in lexical restricted-global check

[3zrv]

fixes: #63715

A top-level lexical declaration (let/const) that collides with a non-configurable ("restricted") own property on a vm context's global object is no longer rejected with a SyntaxError, violating ES#sec-globaldeclarationinstantiation step 5.d.

This is a regression between v24.x and v26.x, found via the test262 case language/global-code/script-decl-lex-restricted-global.js.

const vm = require('vm');
const context = vm.createContext({});
vm.runInContext(
  "Object.defineProperty(this, 'foo', { value: 1, configurable: false });",
  context);
vm.runInContext('let foo;', context);
// v24.12.0: SyntaxError: Identifier 'foo' has already been declared
// v26.3.0:  silently accepted  <-- bug

Root cause

V8's Execution::NewScriptContext (deps/v8/src/execution/execution.cc) checks for a restricted global with LookupIterator::OWN_SKIP_INTERCEPTOR. vm globals are interceptor-backed and keep script-defined properties on a sandbox object, so skipping interceptors hides them and the collision goes undetected. The sibling var/function path in runtime-scopes.cc already keeps interceptors for the non-var case; the lexical path skipping them is the asymmetry that regressed.

Fix

Switch that lookup to LookupIterator::OWN (interceptor-respecting) and propagate a possible pending exception instead of CHECK-ing. No-op for ordinary globals; restores correct behavior for vm contexts.

Upstreaming

This is an interim floating patch; upstreaming to V8 is tracked/forthcoming

Testing

• Added a regression test to test/parallel/test-vm-global-property-interceptors.js.
• The repro now throws SyntaxError: Identifier 'foo' has already been declared.
• All test/parallel/test-vm-* tests pass against a local release build.

[nodejs-github-bot]

Review requested:

• @nodejs/security-wg
• @nodejs/v8-update

[Renegade334]

This is an interim floating patch; upstreaming to V8 is tracked/forthcoming

That's not how it works; see https://github.com/nodejs/node/blob/main/doc/contributing/maintaining/maintaining-V8.md#unfixed-upstream-bugs