ci: add wasm32v1-none target for Rust 1.84+ WASM builds

Fixes getrandom/duplicate lang item errors in WASM builds by ensuring
the wasm32v1-none target is installed before running cargo builds that
involve WASM compilation. This is required for Rust 1.84+ where the
bizinikiwi-wasm-builder uses wasm32v1-none instead of wasm32-unknown-unknown.

Affected workflows:
- tests.yml (quick-benchmarks)
- tests-linux-stable.yml (test-linux-stable-int, test-linux-stable-runtime-benchmarks)
- tests-misc.yml (test-deterministic-wasm)
- build-publish-images.yml (build-linux-stable, build-linux-bizinikiwi)
- check-pezframe-omni-bencher.yml (quick-benchmarks-omni, run-pezframe-omni-bencher)

.github/workflows/tests-linux-stable.yml

@@ -36,6 +36,8 @@ jobs:
     steps:
       - name: Checkout
         uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8 # v5.0.0
+      - name: Install wasm32v1-none target
+        run: rustup target add wasm32v1-none
       - name: script
         id: required
         run: WASM_BUILD_NO_COLOR=1 cargo test -p pezstaging-node-cli --release --locked -- --ignored
@@ -56,6 +58,8 @@ jobs:
     steps:
       - name: Checkout
         uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8 # v5.0.0
+      - name: Install wasm32v1-none target
+        run: rustup target add wasm32v1-none
       - name: script
         id: required
         run: cargo nextest run --workspace --features runtime-benchmarks benchmark --locked --cargo-profile testnet --cargo-quiet