fix: remove wasm32v1-none target for serde_core + Rust 1.88 bug

WASM builds were failing with getrandom/serde_core error when using
wasm32v1-none target. By removing the 'rustup target add wasm32v1-none'
step, wasm-builder will automatically fallback to wasm32-unknown-unknown.

Jobs fixed:
- build-linux-stable
- build-linux-stable-pezcumulus
- build-test-teyrchain
- build-test-collators
- build-malus
- build-linux-bizinikiwi
- build-templates-node
- tests-evm differential and evm-tests
- test-node-metrics

Tracking: https://github.com/pezkuwichain/pezkuwi-sdk/issues/358

.github/workflows/tests-evm.yml

@@ -45,8 +45,8 @@ jobs:
           curl -Lsf --show-error -o resolc "$ASSET_URL"
           chmod +x resolc
           ./resolc --version
-      - name: Add wasm32v1-none target
-        run: rustup target add wasm32v1-none
+      # NOTE: wasm32v1-none target removed - serde_core + Rust 1.88 bug
+      # wasm-builder will fallback to wasm32-unknown-unknown automatically
       - name: Building the dependencies from the Pezkuwi SDK
         run: cargo build --locked --profile release -p pezpallet-revive-eth-rpc -p pez-revive-dev-node
       - name: Checkout the Differential Tests Repository
@@ -119,8 +119,8 @@ jobs:
       - name: Checkout
         uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8 # v5.0.0
 
-      - name: Add wasm32v1-none target
-        run: rustup target add wasm32v1-none
+      # NOTE: wasm32v1-none target removed - serde_core + Rust 1.88 bug
+      # wasm-builder will fallback to wasm32-unknown-unknown automatically
       - name: script
         run: |
           cargo build --locked --release -p pezpallet-revive-eth-rpc --bin eth-rpc