test: bound the swiftc and xcrun calls so a stalled toolchain fails fast

This test compiles a Swift harness with execFileSync and no timeout, so a
contended runner hangs the suite until the job-level timeout instead of
failing it. That now matters more: the new regressions job gates tag
creation, so a hang blocks a legitimate release rather than just a build.

Investigated after a single unreproducible failure (12 runs clean). It is
not a port race -- the server binds with listen(0) and the kernel assigns a
free port. The unbounded toolchain calls are the actual exposure.

Author: Fei-Away

macos/tests/bounded-community-http.test.mjs

@@ -22,6 +22,7 @@ function sdkPath() {
   if (existsSync(known)) return known;
   return execFileSync("/usr/bin/xcrun", ["--sdk", "macosx", "--show-sdk-path"], {
     encoding: "utf8",
+    timeout: 60_000,
   }).trim();
 }
 
@@ -79,13 +80,15 @@ test("bounded community HTTP client", {
   const binary = path.join(temporary, "bounded-community-http-test");
   try {
     const arch = process.arch === "arm64" ? "arm64" : "x86_64";
+    // No timeout here means a contended CI runner can hang the whole suite
+    // instead of failing it, and this test now gates tag creation.
     execFileSync("/usr/bin/swiftc", [
       "-sdk", sdkPath(),
       "-target", `${arch}-apple-macosx13.0`,
       source,
       harness,
       "-o", binary,
-    ], { stdio: "pipe" });
+    ], { stdio: "pipe", timeout: 180_000 });
     await new Promise((resolve, reject) => {
       server.once("error", reject);
       server.listen(0, "127.0.0.1", resolve);