src,node-api: fatal errors should not assume a current isolate may exist

[legendecas]

Fixes a segment fault on Environment::GetCurrent(isolate) on fatal error.

napi_fatal_error and node watchdog triggers fatal error but rather
running on a thread that holds no current isolate.

[nodejs-github-bot]

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

• Linux Containered:
  • parallel/test-domain-error-types

[jasnell]

The CI failure appears to be relevant to this change (that is, it's not just a flaky failure)

[legendecas]

@jasnell which one do you refer to? I checked out https://ci.nodejs.org/job/node-test-pull-request/38033/ and found out the failing case is "parallel/test-domain-error-types" which doesn't seem to be related to this change.

[nodejs-github-bot]

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

• Linux One:
  • pummel/test-crypto-timing-safe-equal-benchmarks

[nodejs-github-bot]

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

• Windows:
  • sequential/test-worker-prof
• Linux One:
  • pummel/test-crypto-timing-safe-equal-benchmarks
  • sequential/test-net-connect-econnrefused

[nodejs-github-bot]

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

• Linux One:
  • pummel/test-crypto-timing-safe-equal-benchmarks

[legendecas]

The linux one case is also failing on PRs like: #38665 (comment)

[mhdawson]

Suggested change

	ABORT();
	fflush(stderr);
	ABORT();

LGTM once my suggestion is incorporated.

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

Linux One:

• pummel/test-crypto-timing-safe-equal-benchmarks

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

Landed in f536cc2