fix(compile): init dummy stdin after debug env is initialized (#29144)

This should be the last change to fix
#27730 and
#21091

The dummy stdin needed when using `--no-terminal` instantly closes, but
closing can't be done until the debug environment is initialized.

This PR delays creation (and closing) of the stdin until after the debug
environment is initialized.

Co-authored-by: Divy Srivastava <[email protected]>

Author: JasperVanEsveld

ext/node/polyfills/process.ts

@@ -996,12 +996,6 @@ internals.__bootstrapNodeProcess = function (
     core.setMacrotaskCallback(runNextTicks);
     enableNextTick();
 
-    // Replace stdin if it is not a terminal
-    const newStdin = initStdin();
-    if (newStdin) {
-      stdin = process.stdin = newStdin;
-    }
-
     // Replace stdout/stderr if they are not terminals
     if (!io.stdout.isTerminal()) {
       /** https://nodejs.org/api/process.html#process_process_stdout */
@@ -1025,6 +1019,12 @@ internals.__bootstrapNodeProcess = function (
 
     initializeDebugEnv(nodeDebug);
 
+    // Replace stdin if it is not a terminal
+    const newStdin = initStdin();
+    if (newStdin) {
+      stdin = process.stdin = newStdin;
+    }
+
     delete internals.__bootstrapNodeProcess;
   } else {
     // Warmup, assuming stdin/stdout/stderr are all terminals