fix: prevent crash on web-contents creation when error is thrown

[VerteDinde]

Description of Change

Fixes #28749

Currently, if an unhandled error is thrown during web-contents creation on a new browser window within JavaScript's scope, the error is not being correctly bubbled up, causing a DCHECK and hard app crash. More specifically, here are the steps that could lead to a crash (thanks @MarshallOfSound for the breakdown!):

• User's JS code triggers some native code
• The native code emits an event
• The event is emitted in the same scope as the JS code that triggered the native code
• The event handler throws an error
• The native code then tries to run more JS (emit another event, call a getter, etc.), which cannot happen because there is a pending exception

This PR adds Node's exception error handler to the _init method for web-contents creation, bubbling the error into a different scope and allowing us to handle it more appropriately, rather than hard crashing.

Checklist

• PR description included and stakeholders cc'd
• npm test passes
• tests are changed or added
• relevant documentation is 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 an exception occurs within the event emitter.

[zcbenz]

Can you add test for this? Putting https://gist.github.com/nornagon/2b0373a300af0931c0c29b0e8dff8b73 under spec-main/fixtures/crash-cases/ should be enough.

[VerteDinde]

@zcbenz Will do! Thanks for reviewing! 🙂

[release-clerk]

Release Notes Persisted

Fix crash when an exception occurs within the event emitter.

[trop]

I have automatically backported this PR to "13-x-y", please check out #29106