Stabilize frontend coverage tests on Zoomies CI runners

[Copilot]

The Frontend (React) GitHub Actions job was failing in the coverage test step after the runner migration, with otherwise unrelated UI tests timing out or missing async-rendered elements. This change narrows the fix to the frontend test harness so CI gets more headroom without changing application behavior.

• Root cause

  • Coverage-instrumented Vitest runs on the new runners were slower than local/default expectations.
  • Multiple failures were symptoms of the same issue: default test and async-query timeouts expiring before the DOM settled.

• What changed

  • Vitest CI timeout
    • Add a CI-only testTimeout override in frontend/vitest.config.ts.
  • Testing Library CI async wait
    • Configure a longer CI-only asyncUtilTimeout in frontend/src/test-setup.ts.

• Effect

  • Keeps local feedback fast.
  • Reduces CI-only flakes in async-heavy page tests under coverage.

// frontend/vitest.config.ts
test: {
  environment: 'jsdom',
  globals: true,
  setupFiles: ['./src/test-setup.ts'],
  testTimeout: process.env.CI ? 10000 : 5000,
}

// frontend/src/test-setup.ts
configure({
  asyncUtilTimeout: process.env.CI ? 5000 : 1000,
})

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.