fix(ext/node): include prototype env vars in child_process spawn (#32699)

The env key collection loop had `Object.hasOwn()` filtering despite the
comment saying "Prototype values are intentionally included". This made
`for...in` pointless since it only kept own properties.

Node.js includes prototype-chain env vars when spawning child processes,
and this test explicitly verifies that behavior.

Author: fraidev

ext/node/polyfills/internal/child_process.ts

@@ -1148,10 +1148,9 @@ export function normalizeSpawnArguments(
 
   let envKeys: string[] = [];
   // Prototype values are intentionally included.
+  // deno-lint-ignore guard-for-in
   for (const key in env) {
-    if (Object.hasOwn(env, key)) {
-      ArrayPrototypePush(envKeys, key);
-    }
+    ArrayPrototypePush(envKeys, key);
   }
 
   if (process.platform === "win32") {

tests/node_compat/config.jsonc

@@ -205,6 +205,7 @@
     "parallel/test-child-process-detached.js": {},
     "parallel/test-child-process-disconnect.js": {},
     "parallel/test-child-process-double-pipe.js": {},
+    "parallel/test-child-process-env.js": {},
     "parallel/test-child-process-exec-cwd.js": {},
     "parallel/test-child-process-exec-env.js": {},
     "parallel/test-child-process-exec-error.js": {},