Console reader permanently dies on Linux when fd 0 becomes non-blockin

Describe the bug

On Linux, the server console stops responding to typed commands after a plugin/component puts stdin (fd 0) into non-blocking mode.
The Console still echoes keystrokes and accepts Enter, but no command is executed and even Unknown command or variable: is never printed.

Windows is unaffected, Under Windows, the Node environment does not receive events from stdin.
However, this changes under Linux.

To Reproduce

This is a edge case, I encountered it in the samp-node environment, but I suspect that omp-node same.
I have tried passing kNoStdioInitialization to node::InitializeOncePerProcess, but it seems to have no effect.
This probably caused by node libuv behavior.

I don't know if the same issue exists for stdin in other languages, such as omp-rs, ompgo, sampsharp?
You will encounter it when you use the node:process, and many packages you depend on will be used, such as mysql.

import process from "node:process";
process.stdin.on('data', (chunk) => {
  console.log(`Received data: ${chunk}`);
});

Enter anything on the console, such as foo
For the first time, you can see something like Unknown command or variable: foo
After that, no matter what you type in, there's just an echo

Expected behavior

Console should remain in blocking mode of fd0 and should not be affected by plugins or components for compatibility.

Screenshots and/or logs

Showing echo but no server response.
No crash, no error in the log.

Commit hash in master

91a38854

Additional context
I've already run one actions, so if anyone needs to test?
https://github.com/dockfries/open.mp/actions/runs/34498389091