fix: filter exceptions passed to blink message handler

[zcbenz]

Description of Change

This is a partial fix for #37404.

Blink installs a global V8 message handler to print exceptions to devtools, which will crash when seeing an exception from a foreign context. Since we can not prevent Node from using a non-blink context (from vm module, or from native modules, or from Node's internal code), we should add a wrapper to prevent blink from accessing foreign contexts in the message handler.

Checklist

• PR description included and stakeholders cc'd
• npm test passes
• tests are changed or added
• relevant documentation, tutorials, templates and examples are changed or added
• PR release notes describe the change in a way relevant to app developers, and are capitalized, punctuated, and past tense.

Release Notes

Notes: Fix crash when throwing exception from context created by Node.js vm module.

[MarshallOfSound]

I believe this check is present for security reasons in blink, this effectively changes the check to be a no-op if I'm reading this right as any maliciously created context will be allowed to leak between blink worlds.

There was a discussion at one point around simply disabling vm in the renderer process, I think that should be revisited instead of consistently patching around something that blink does not intend to operate with

[zcbenz]

The blink message handler is where blink captures exceptions and errors and print them out to the devtools, what this PR does is to check whether the exceptions and errors come from blink, and only handle them to the blink message handler if so. It does not disable blink's security check on contexts, blink still crashes when seeing a foreign context, I don't this PR would introduce any security issue.

[zcbenz]

I'm closing this PR since https://github.com/electron/electron/blob/main/patches/chromium/fix_harden_blink_scriptstate_maybefrom.patch provides a better way to fix the issue.