vm: TypeError thrown instead of ReferenceError when a Proxy is the vm context

### Version v22.7.0 ### Platform ```text Microsoft Windows NT 10.0.22631.0 x64 ``` ### Subsystem vm ### What steps will reproduce the bug? ```js "use strict"; const vm = require("vm"); const context = vm.createContext({ __proto__: new Proxy({}, { get(target, property, receiver) { return Reflect.get(target, property, receiver); } }) }); vm.runInContext("thisFunctionDoesNotExist()", context); ``` Output: ### How often does it reproduce? Is there a required condition? Always. ### What is the expected behavior? Why is that the expected behavior? If I instead do ```js const context = vm.createContext({ __proto__: new Proxy({}, {}) }); vm.runInContext("thisFunctionDoesNotExist()", context); ``` or simply ```js const context = vm.createContext({}); vm.runInContext("thisFunctionDoesNotExist()", context); ``` then I get the expected output: ``` $ node test.js evalmachine.<anonymous>:1 thisFunctionDoesNotExist() ^ ReferenceError: thisFunctionDoesNotExist is not defined at evalmachine.<anonymous>:1:1 at Script.runInContext (node:vm:148:12) at Object.runInContext (node:vm:300:6) ``` ### What do you see instead? ```$ node test.js evalmachine.<anonymous>:1 thisFunctionDoesNotExist() ^ TypeError: thisFunctionDoesNotExist is not a function at evalmachine.<anonymous>:1:1 at Script.runInContext (node:vm:148:12) at Object.runInContext (node:vm:300:6) at Object.<anonymous> (C:\Users\d\OneDrive - domenic.me\Code\GitHub\jsdom\jsdom\test.js:31:4) at Module._compile (node:internal/modules/cjs/loader:1546:14) at Module._extensions..js (node:internal/modules/cjs/loader:1691:10) at Module.load (node:internal/modules/cjs/loader:1317:32) at Module._load (node:internal/modules/cjs/loader:1127:12) at TracingChannel.traceSync (node:diagnostics_channel:315:14) at wrapModuleLoad (node:internal/modules/cjs/loader:217:24) Node.js v22.7.0 ``` ### Additional information I am not 100% sure this is a vm bug. It may be a fundamental li…