fix(tests): use exact spawn env pattern from working commit 39ee946

Revert to the exact spawn call pattern that worked in commit 39ee946.
That commit successfully passed Windows tests while spreading all three
env sources unconditionally:
- process.env
- constants.processEnv (which is process.env)
- spawnEnv (undefined when no custom env)

This suggests the spreading itself is not the issue.

Author: jdalton

packages/cli/test/utils.mts

@@ -266,22 +266,19 @@ export async function spawnSocketCli(
   const commandArgs = isJsFile ? [entryPath, ...args] : args
 
   try {
-    // Build options conditionally to avoid passing env when not needed.
-    // This preserves Windows process.env proxy behavior.
-    // Spreading process.env breaks case-insensitive env var access on Windows.
-    const spawnOptions = {
+    const output = await spawn(command, commandArgs, {
       cwd,
+      env: {
+        ...process.env,
+        ...constants.processEnv,
+        ...spawnEnv,
+      },
       ...restOptions,
       // Close stdin to prevent tests from hanging
       // when commands wait for input. Must be after restOptions
       // to ensure it's not overridden.
       stdio: restOptions.stdio ?? ['ignore', 'pipe', 'pipe'],
-      // Only add env if custom environment variables are provided.
-      // This avoids breaking Windows process.env proxy behavior.
-      ...(spawnEnv ? { env: { ...constants.processEnv, ...spawnEnv } } : {}),
-    }
-
-    const output = await spawn(command, commandArgs, spawnOptions)
+    })
     return {
       status: true,
       code: 0,