test(hub-selection): raise windows-flaky beforeAll/test timeouts to 60s

[carlos-alm]

Problem

tests/unit/hub-selection.test.ts has now hit the default 30s hook/test timeout on Test Node 22 (windows-2022) across multiple independent, otherwise-unrelated PRs this session (a docs-only README badge change, a lockfile-only chore, and two of my own earlier PRs in this /fixer run) — always the same two spots:

• The beforeAll hook (fs.mkdtempSync + a fresh better-sqlite3 file + schema init).
• The 'throws when the graph has no qualifying nodes with edges' test, which does its own separate mkdtempSync + DB file (unlike every other test in the file, which reuses the single DB beforeAll already built).

Every occurrence reran cleanly on retry — this is Windows-runner I/O slowness (the full Windows suite run is consistently ~470-500s, close to whatever margin exists before hitting the 30s per-hook/per-test ceiling), not a real regression in this file or whatever the triggering PR happened to touch.

Fix

Raised both to a 60s timeout via vitest's per-hook/per-test override — mirrors the identical fix already applied to a different Windows-flaky test in this repo (tests/unit/lint-skill-read-binding-2344.test.ts, PR #2490).

Did not pursue the issue's other two suggested options:

• The I/O itself (mkdtempSync + a small sqlite init) isn't doing anything unusually slow — nothing to speed up algorithmically; the slowness is Windows-runner-environmental.
• A "known-flaky" allowlist would still require someone to notice and rerun the failure each time — the timeout increase actually prevents the failure from happening in the first place.

Closes #2368

Test plan

• vitest run tests/unit/hub-selection.test.ts — all 6 tests pass
• Full vitest run suite (5283 passed, 328 files) after rebuilding the native addon (stale in the fresh worktree, unrelated to this test-only change)
• tsc --noEmit, biome check clean

[greptile-apps]

Greptile Summary

This PR raises two Windows-flaky timeout limits in the hub-selection unit tests from the configured 30 seconds to 60 seconds.

• Adds a 60-second timeout to the shared beforeAll database setup.
• Adds a 60-second timeout to the test that creates a separate temporary SQLite database.

Confidence Score: 5/5

The PR appears safe to merge because both timeout forms are supported and honored by the repository’s Vitest version.

The changes only extend timeout allowances for existing test setup and execution paths, with no accepted functional, security, or quality defects.

Important Files Changed

Filename	Overview
tests/unit/hub-selection.test.ts	Applies valid Vitest timeout overrides to two slow Windows CI paths without changing test behavior or production code.

_{Reviews (1): Last reviewed commit: "test(hub-selection): raise windows-flaky..." | Re-trigger Greptile}