fix(e2e): give the harness tests a timeout they can actually meet

[CAMOBAP]

The e2e harness suite has been failing on master on every run since at least 2026-08-16.
It is not flaky and not environmental — it cannot pass as configured.

Each case in darkTheme.harness.js does:

await render(<WidgetFixture theme="light" />, { timeout: WEBVIEW_LOAD_MS }); // 10s
await new Promise((r) => setTimeout(r, WEBVIEW_LOAD_MS));                    // + 10s

so it needs over 20s. No testTimeout was set anywhere in the repo, so Jest's 5s default
applied and the test was killed mid-sleep every time:

✕ light widget matches baseline (5045 ms)
  Test timed out after 5000ms: hCaptcha theme rendering light widget matches baseline
  Pending promises at timeout: 1

The second case never ran (○ skipped), so neither baseline has actually been compared in
months.

This sets testTimeout: 60000 — 20s is the floor, the rest is headroom for a cold emulator
and the screenshot compare.

Follow-up worth doing separately

The fixed setTimeout(10000) settle is a guess: too slow locally, too fragile on a loaded
runner. Driving the fixture off the component's readiness signal instead would make each case
wait exactly as long as it needs and cut ~20s per case. Left out here to keep this PR to the
one-line unblock, since changing when the screenshot is taken may require regenerating the
baselines.

🤖 Generated with Claude Code