Fix the Pages build: install wasm-bindgen-cli at the Cargo.lock version

The workflow pinned wasm-bindgen-cli 0.2.100 while the wasm module linked
wasm-bindgen 0.2.126, and the bindgen schema must match exactly, so the deploy
failed at the bindings step. Read the version out of Cargo.lock at install time
so the CLI and the crate can never drift apart again.

Author: Axmouth

.github/workflows/pages.yml

@@ -30,7 +30,13 @@ jobs:
         with:
           targets: wasm32-unknown-unknown
       - name: Install wasm-bindgen-cli
-        run: cargo install wasm-bindgen-cli --version 0.2.100 --locked || cargo install wasm-bindgen-cli --locked
+        # The CLI's bindgen schema must exactly match the wasm-bindgen crate the wasm module was
+        # built against, so read the version from Cargo.lock rather than pinning it here, and the
+        # two can never drift apart.
+        run: |
+          VERSION=$(grep -A1 'name = "wasm-bindgen"' Cargo.lock | grep version | head -1 | cut -d'"' -f2)
+          echo "wasm-bindgen crate version from Cargo.lock: $VERSION"
+          cargo install wasm-bindgen-cli --version "$VERSION" --locked
       - name: Build web artifacts
         run: ./tools/build_web.sh
       - uses: actions/upload-pages-artifact@v3