fix(node/stream): handle 'close' event in fromReadable to prevent Windows hang

On Windows, when a child process terminates, its stdio streams may emit
'close' without first emitting 'end'. Since fromReadable only listened
for 'end' to close the signal, the Effection subscription would never
complete. This caused the Win32 exec implementation to hang forever
waiting for stdoutDone/stderrDone resolvers that gate on stream drain.

Adding a 'close' listener ensures the signal closes regardless of
which event the platform emits first. The signal.close() call is
idempotent, so receiving both 'end' and 'close' is safe.

Author: Taras Mankovski

node/stream.ts

@@ -38,13 +38,15 @@ export function fromReadable(target: Readable): Stream<Uint8Array, void> {
 
     target.on("data", listener);
     target.on("end", signal.close);
+    target.on("close", signal.close);
     target.on("error", errorHandler);
 
     try {
       yield* provide(yield* signal);
     } finally {
       target.off("data", listener);
       target.off("end", signal.close);
+      target.off("close", signal.close);
       target.off("error", errorHandler);
       signal.close();
     }