test(e2e): bump preview-render timeout to 75s under CI load

PR #172's first pull_request-triggered run hit a worker-contention
timeout in metadata/format-specific/doc-format-overrides.qmd — the
preview iframe didn't render within 45s on any of the 3 attempts.
Same shape as the failures we saw with 4 workers (cleared by dropping
to 2), but now appearing at 2 workers because the runner happened to
be slower this time. 8 other smoke-all tests passed only on retry,
i.e. they were right at the edge.

Bump waitForPreviewRender from 45s to 75s, and the per-test ceiling
from 60s to 90s so the wider preview wait can actually fire. Fast
tests still pass fast; slower fixtures under contention get the
breathing room they need.

Author: gordonwoodhull

hub-client/e2e/smoke-all.spec.ts

@@ -35,8 +35,12 @@ const allTests: DiscoveredTest[] = discoverSmokeAllTests();
 // ---------------------------------------------------------------------------
 
 test.describe('smoke-all E2E tests', () => {
-  // Increase timeout for SASS compilation tests
-  test.setTimeout(60000);
+  // Increase timeout for SASS compilation tests. On a contended CI
+  // runner (ubuntu-latest with 2 cores, 2 workers, a vite dev server,
+  // the hub binary, and chromium per worker) the preview render can
+  // take 30-50s for the slower fixtures. 90s leaves headroom for the
+  // 75s waitForPreviewRender wait below to actually fire.
+  test.setTimeout(90000);
 
   for (const fixture of allTests) {
     const skipReason = shouldSkip(fixture.runConfig, fixture.relPath);
@@ -108,7 +112,7 @@ test.describe('smoke-all E2E tests', () => {
         // Wait for render (or error)
         if (!spec.expectsError) {
           await waitForPreviewRender(page, {
-            timeout: 45000,
+            timeout: 75000,
             consoleErrors,
             kind,
           });