Stabilize Axe scans on cold Windows CI runners

[zhaowl94]

What changed

• give only test/e2e/accessibility.spec.mjs a 60-second Playwright timeout
• retain the 30-second default for every other browser test
• keep retries disabled, so real failures are not hidden

Root cause

The first master deployment workflow completed 162 of 163 Windows browser tests. Firefox's Axe scan for /index.html took 38.4 seconds on a cold GitHub-hosted Windows runner and crossed the former 30-second global limit. The log contained no accessibility violation; the identical commit had already passed the PR workflow and local matrices.

Impact

This gives the intentionally heavier Axe scans enough cold-start headroom without relaxing functional, keyboard, security, visual, or Windows Edge test timeouts. Site runtime code and output are unchanged.

Validation

• Firefox Axe pressure run: 30/30 passed across three repetitions
• Windows browser matrix: 163/163 passed
• isolated Ubuntu browser/visual matrix: 142/142 passed
• unit tests: 7/7 passed
• static, HTML, CSS, JavaScript, path, CSP, and payload checks passed
• dependency audit: 0 vulnerabilities
• five external links returned HTTP 200
• Lighthouse: performance, accessibility, best practices, and SEO all scored 1.00 on five representative pages