fix: let Node.js perform microtask checkpoint in the main process

[deepak1556]

Description of Change

Closes #23838.
Refs #20013 (comment)

Checklist

• PR description included and stakeholders cc'd
• npm test passes
• tests are changed or added
• relevant documentation is changed or added
• 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.
• This is NOT A BREAKING CHANGE. Breaking changes may not be merged to master until 11-x-y is branched.

Release Notes

Notes: fix delayed execution of some Node.js callbacks in the main process

[codebytere]

@deepak1556 i think this fixes #23838

const f3 = async () => {
    return new Promise((_, reject) => {
        reject('oops');
    });
}

f3().catch((error) => {
   console.log('3 caught', error);
});

should function as a minimal test case if run in the main proc

Right now it errors like so:

(node:86234) UnhandledPromiseRejectionWarning: oops
(node:86234) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:86234) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
3 caught oops
(node:86234) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 1)

because the catch is happening on a subsequent tick, one farther than it should, and there are two promises happening (the async wrapper and the promise itself) which lines up with what you're describing here

See #23838 (comment) :)

[deepak1556]

Thanks @codebytere , yep that does serve as a valid test case.

[zcbenz]

On the failed getGPUInfo test, it is because with this change the resolve/reject callbacks get called earlier and then results in a call like this:

w.webContents.once('did-finish-load', () => {
  app.exit(1)
})

Which then crashes.

Schedule the app.exit into next tick in gpu-info.js should be able to fix the failed test, though we should look into solving the crash in future.

[release-clerk]

Release Notes Persisted

fix delayed execution of some Node.js callbacks in the main process

[trop]

I was unable to backport this PR to "8-x-y" cleanly;
you will need to perform this backport manually.

[trop]

I was unable to backport this PR to "9-x-y" cleanly;
you will need to perform this backport manually.

[trop]

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

[trop]

@deepak1556 has manually backported this PR to "9-x-y", please check out #24178

[trop]

@deepak1556 has manually backported this PR to "8-x-y", please check out #24180