deploy: keep Monaco WASM raw

[alixander]

What changed

• remove the post-deploy Brotli rewrite of dist/js/vendor/onig.wasm
• keep WASM assets raw throughout the deploy and any subsequent mirror
• retain the existing explicitly encoded JS and CSS uploads

Why

The deploy script synced dist first and then replaced dist/js/vendor/onig.wasm with Brotli bytes without uploading it or attaching Content-Encoding metadata. Reusing that mutated directory for the source-account mirror stored compressed bytes as an ordinary WASM object. The live CloudFront distribution compressed it again, and browsers received Brotli bytes instead of the WebAssembly magic header, preventing Monaco from initializing.

Keeping WASM raw makes the build directory safe to re-sync and mirror. Any future precompression must use matching object metadata.

Impact

Future playground deploys and mirrors will publish a directly usable onig.wasm instead of leaving a hazardous post-deploy artifact. This does not change the explicit Brotli handling for the large JavaScript and CSS bundles.

Validation

• bash -n ci/deploy.sh
• git diff --check

No new test was added.