fix(hub-client): raise PWA precache size limit so WASM growth stops breaking CI

The workbox `maximumFileSizeToCacheInBytes` ceiling was 35MB while the
`wasm_quarto_hub_client_bg.wasm` artifact had crept to ~36.7MB. When a
globbed precache asset exceeds the limit, workbox emits a warning that
vite-plugin-pwa's `logWorkboxResult` throws as a fatal build error,
failing `vite build` (and thus the TS Test Suite's Build WASM step).

The boundary was razor-thin: the local/ubuntu build landed just under
35MiB while the macOS CI build produced ~990 bytes over, so main went
red only on macOS after #379 (render_printable + self-contained
inliner) grew the WASM.

Raise the ceiling to 64MB to restore generous headroom for continued
WASM growth.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: cscheid

hub-client/vite.config.ts

@@ -114,8 +114,12 @@ export default defineConfig({
       workbox: {
         // Precache all static assets including JS/CSS bundles and WASM
         globPatterns: ['**/*.{html,js,css,svg,woff,woff2,wasm}'],
-        // Increase limit to 35MB to include WASM files (largest is ~32MB)
-        maximumFileSizeToCacheInBytes: 35 * 1024 * 1024,
+        // Increase limit to include WASM files (largest is ~37MB and growing).
+        // Keep generous headroom: when a globbed asset exceeds this limit
+        // workbox emits a warning that vite-plugin-pwa throws as a fatal
+        // build error, so a too-tight ceiling breaks CI the moment the WASM
+        // creeps past it (see the 35MB ceiling that broke main after #379).
+        maximumFileSizeToCacheInBytes: 64 * 1024 * 1024,
         // Don't warn about large files - we know they're big
         dontCacheBustURLsMatching: /\.[0-9a-f]{8}\./,
         runtimeCaching: [