Give the private browser checks 90 s per test (#66)

On Docker-Builder1 the emulator comparisons now exceed Playwright's 30 s
default (13 Chromium parity tests in run 136) although they pass locally
in under 10 s. The job limit rises to 60 minutes to fit the slower runs.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

.gitea/workflows/private-checks.yml

@@ -12,7 +12,7 @@ jobs:
     runs-on: docker-build
     container:
       image: node:22-bookworm
-    timeout-minutes: 40
+    timeout-minutes: 60
     env:
       CRYSTAL_ROM_PATH: .reference/ci/crystal.gbc
     steps:
@@ -46,8 +46,9 @@ jobs:
         run: npm test -- --maxWorkers=2
       - run: npx playwright install --with-deps chromium webkit
       # One worker: with two, the runner host dropped off mid-run (runs 122, 130, 132, 134).
+      # The emulator comparisons can take over 30 s each on this host (run 136).
       - name: Chromium and WebKit gameplay and reference comparisons
-        run: npm run test:e2e -- --workers=1 --trace=off
+        run: npm run test:e2e -- --workers=1 --timeout=90000 --trace=off
       - name: Remove private data and browser output
         if: always()
         run: rm -rf .reference test-results playwright-report test-saves