fix: isolate callbacks in node_bindings

[codebytere]

Description of Change

While some aspects of embedding are necessarily different between emulated Node.js and Node.js as it's embedded in the main and renderer processes of Electron, there's been some skew recently in our embedding processes resultant of the fact that we only test some of Node's functionality in emulated mode and therefore miss potential holes in non-emulated mode.

In the future, we should seek to test these more effectively, but for now we should at least close that gap by ensuring that isolate setup is better executed in non-emulated mode. There remains some work to be done here around async_hooks (see #23213) but that will require a little more investigation to determine what of SetupIsolateForNode can be safely executed in a non-emulated environment without causing collateral damage.

cc @nornagon @ckerr @MarshallOfSound

Checklist

• PR description included and stakeholders cc'd
• npm test passes
• PR title follows semantic commit guidelines
• PR release notes describe the change in a way relevant to app developers, and are capitalized, punctuated, and past tense.

Release Notes

Notes: Fixed some Wasm and diagnostics issues in main and renderer process execution of Node.js

[release-clerk]

Release Notes Persisted

Fixed some Wasm and diagnostics issues in main and renderer process execution of Node.js