fix(test): force-exit routes.test.js worker on Windows after suite completes

After all Routes subtests finish, node-pty's conpty_console_list_agent.js
helper process can crash with `AttachConsole failed` and keep stdio pipes
dangling on the test worker, preventing it from exiting before the per-file
--test-timeout (180s) fires. The whole file then gets marked as failed
even though every individual assertion passed.

The earlier --test-force-exit flag (added to npm test) only acts on the
parent test runner — it has no effect on per-file workers under
--test-isolation=process. Targeted Windows-only after() hook now schedules
a process.exit(0) with a 1.5s unref'd grace period, letting in-flight
pty.kill IPC settle before forcing the worker out. Non-Windows runs
keep full process-leak detection.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: dorlugasigal

test/server/routes.test.js

@@ -4976,4 +4976,25 @@ describe('Routes', () => {
       });
     },
   );
+
+  /*
+   * Windows-only worker-exit shim. After every Routes subtest completes,
+   * node-pty's `conpty_console_list_agent.js` helper process can crash with
+   * `AttachConsole failed` and keep our test worker's event loop alive on
+   * dangling stdio pipes. The per-file --test-timeout (180s) then fires
+   * and marks the WHOLE file as failed even though every assertion passed.
+   *
+   * `--test-force-exit` doesn't help here — that flag only acts on the
+   * parent test runner, not on per-file worker processes.
+   *
+   * After every test in this file has reported, force-exit the worker
+   * itself with a brief grace period for any in-flight `pty.kill()`
+   * IPC to settle. Skipped on non-Windows so we still get full process
+   * leak detection on Linux/macOS.
+   */
+  if (process.platform === 'win32') {
+    after(() => {
+      setTimeout(() => process.exit(0), 1500).unref();
+    });
+  }
 });