build: enable bulk-memory in release wasm-opt

	runk build --release failed with a flood of wasm-validator errors
along the lines of:

    [wasm-validator error in function NNNN] unexpected false:
    memory.copy operations require bulk memory operations
    [--enable-bulk-memory-opt]

Trunk's bundled wasm-opt (binaryen v123) does not enable the
bulk-memory feature by default, but rustc 1.82+ (and several of our
dependencies) emit `memory.copy` instructions, so wasm-opt rejects
the staged wasm before it can be optimised.

Forward `--enable-bulk-memory` and `--enable-nontrapping-float-to-int`
to wasm-opt via Trunk's `data-wasm-opt-params` attribute on the
`rust` link in `index.html`. These are the same target features
the rustc wasm32 target enables, so the optimiser now accepts the
input and the release pipeline succeeds.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: felipebalbi

index.html

@@ -15,7 +15,20 @@
     <script defer src="https://d3js.org/d3.v7.min.js"></script>
     <script defer src="/repo_graph.js"></script>
 
-    <link data-trunk rel="rust" data-wasm-opt="z" data-keep-debug="false" data-weak-refs />
+    <!--
+      `data-wasm-opt-params` forwards extra flags to wasm-opt. The bundled
+      wasm-opt v123 has bulk-memory disabled by default, but rustc 1.82+
+      emits `memory.copy` instructions, which fail validation. The two
+      `--enable-*` flags below match the features the rustc target enables.
+    -->
+    <link
+      data-trunk
+      rel="rust"
+      data-wasm-opt="z"
+      data-wasm-opt-params="--enable-bulk-memory --enable-nontrapping-float-to-int"
+      data-keep-debug="false"
+      data-weak-refs
+    />
     <link rel="icon" href="images/odpicon.ico" type="image/x-icon">
     <link href="https://fonts.googleapis.com/css2?family=Geist:wght@400;600&display=swap" rel="stylesheet">
   </head>