fix: add wasm32v1-none target to CI workflows

Root cause: CI Docker images don't have wasm32v1-none target installed.
wasm-builder falls back to wasm32-unknown-unknown with -Z build-std=core,alloc
which causes duplicate alloc crate and 'exchange_malloc' lang item error.

Solution: Add 'rustup target add wasm32v1-none' before cargo build steps
in all workflows that build WASM.

Affected workflows:
- checks.yml: cargo-clippy job
- build-publish-images.yml: 11 jobs
- tests-misc.yml: test-node-metrics, test-deterministic-wasm

.github/workflows/tests-misc.yml

@@ -116,6 +116,9 @@ jobs:
           rm -rf ~/.cargo/registry/cache 2>/dev/null || true
           rm -rf ~/.cargo/git/db 2>/dev/null || true
 
+      - name: Add wasm32v1-none target
+        run: rustup target add wasm32v1-none
+
       - name: script
         run: |
           # build runtime
@@ -253,6 +256,9 @@ jobs:
           rm -rf ~/.cargo/registry/cache 2>/dev/null || true
           rm -rf ~/.cargo/git/db 2>/dev/null || true
 
+      - name: Add wasm32v1-none target
+        run: rustup target add wasm32v1-none
+
       - name: Run tests
         id: tests
         env: