fix(worker): consult the termination-requested flag at the last two failure sites

The CommonJS module-function call and the ES module Evaluate failure only
recognized a termination V8 had already materialized. A request that landed
during the call, before any JS ran to materialize it, let an ordinary failure
be formatted as an error on a terminating isolate. Both sites now read the
same three signals as the settle pump and the require path.

Author: edusperoni

NativeScript/runtime/ModuleInternal.mm

@@ -894,7 +894,9 @@ throw NativeScriptException(isolate,
         moduleFunc->Call(context, thiz, sizeof(requireArgs) / sizeof(Local<Value>), requireArgs)
             .ToLocal(&result);
     if (!success || tc.HasCaught()) {
-      if (tc.HasTerminated()) {
+      Runtime* runtime = Runtime::GetRuntime(isolate);
+      if (tc.HasTerminated() || isolate->IsExecutionTerminating() ||
+          (runtime != nullptr && runtime->IsTerminationRequested())) {
         throw NativeScriptException("Module evaluation interrupted by isolate termination: " +
                                     modulePath);
       }
@@ -1295,7 +1297,9 @@ throw NativeScriptException(
     RemoveModuleFromRegistry(isolate, canonicalPath);
     // Same rule as the pump below: a termination outranks any failure detail,
     // and reading the TryCatch as an error would run JS on the dying isolate.
-    if (tcEval.HasTerminated() || isolate->IsExecutionTerminating()) {
+    Runtime* runtime = Runtime::GetRuntime(isolate);
+    if (tcEval.HasTerminated() || isolate->IsExecutionTerminating() ||
+        (runtime != nullptr && runtime->IsTerminationRequested())) {
       LogEsmPhase(canonicalPath, "evaluate", "terminated");
       throw NativeScriptException("Module evaluation interrupted by isolate termination: " +
                                   canonicalPath);