src: try showing stack traces when process._fatalException is not set

[joyeecheung]

So that the stack trace of errors shown in internal code run during
bootstrap (before process._fatalException is set) can be printed.

Refs: #29593

Checklist

• make -j4 test (UNIX), or vcbuild test (Windows) passes
• tests and/or benchmarks are included
• documentation is changed or added
• commit message follows commit guidelines

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/25664/

[joyeecheung]

cc @addaleax @cjihrig @Fishrock123

[joyeecheung]

Before the patch if you make a typo in, e.g. bootstrap/node.js, the error is printed as follows:

internal/bootstrap/loaders.js:191
  if (!mod) throw new TypeError(`Missing internal module '${id}'`);
            ^

TypeError: Missing internal module 'internal/process/per_thread1'

After the patch it looks like this:

internal/bootstrap/loaders.js:191
  if (!mod) throw new TypeError(`Missing internal module '${id}'`);
            ^

TypeError: Missing internal module 'internal/process/per_thread1'
    at nativeModuleRequire (internal/bootstrap/loaders.js:191:19)
    at internal/bootstrap/node.js:51:24

[Trott]

@nodejs/collaborators This one could use some reviews.

[Trott]

Is it reasonable/feasible to add a test?

[Fishrock123]

Works for me.

I can't think of an easy or particularly necessary way to test this (since it should only occur on internal dev mistakes).

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/25673/

[Trott]

Landed in 355f2ad