fix(@angular/build): add bounded timeout to vitest executor disposal

When disposing the VitestExecutor in non-watch runs, `vitest.close()` can hang if a Vitest worker pool process or thread fails to terminate cleanly. Calling `process.exit()` in a builder runner is undesirable as it forcibly kills the host Node.js process and aborts any downstream Architect tasks or reporters.

This change wraps `this.vitest.close()` in a `Promise.race` with an unref'd `setTimeout`. If `close()` stalls beyond 10 seconds, a warning is logged and disposal finishes cleanly, allowing host process execution and downstream logic to proceed.

Fixes #32832

Author: clydin

packages/angular/build/src/builders/unit-test/runners/vitest/executor.ts

@@ -9,6 +9,7 @@
 import type { BuilderContext, BuilderOutput } from '@angular-devkit/architect';
 import assert from 'node:assert';
 import path from 'node:path';
+import { setTimeout } from 'node:timers/promises';
 import type * as Vite from 'vite' with {
   'resolution-mode': 'import',
 };
@@ -207,8 +208,31 @@ export class VitestExecutor implements TestExecutor {
   }
 
   async [Symbol.asyncDispose](): Promise<void> {
+    if (!this.vitest) {
+      return;
+    }
+
     this.debugLog(DebugLogLevel.Info, 'Disposing VitestExecutor: Closing Vitest instance.');
-    await this.vitest?.close();
+
+    const controller = new AbortController();
+    const timeoutMs = 10_000;
+
+    try {
+      await Promise.race([
+        this.vitest.close(),
+        setTimeout(timeoutMs, undefined, { signal: controller.signal, ref: false }).then(() => {
+          this.logger.warn(
+            `Vitest instance failed to close cleanly within ${timeoutMs}ms. Continuing teardown...`,
+          );
+        }),
+      ]);
+    } catch (error: unknown) {
+      assertIsError(error);
+      this.logger.error(`An error occurred while closing Vitest instance: ${error.message}`);
+    } finally {
+      controller.abort();
+    }
+
     this.debugLog(DebugLogLevel.Info, 'Vitest instance closed.');
   }