fix(ci): remove wasm32v1-none target to fix serde_core compilation (#346)

* docs: update workflow plan with completed CI fixes

* fix(ci): remove wasm32v1-none target installation to fix serde_core compilation

This removes the explicit `rustup target add wasm32v1-none` step from CI
workflows. When wasm32v1-none is installed, the wasm-builder uses it instead
of wasm32-unknown-unknown, which causes serde_core 1.0.228 to fail compilation
with "relaxing a default bound only does something for ?Sized" errors.

By not installing wasm32v1-none, the wasm-builder automatically falls back to
wasm32-unknown-unknown which compiles successfully.

This aligns with Polkadot SDK's CI configuration which also does not explicitly
install wasm32v1-none.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>

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

@@ -36,8 +36,6 @@ 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
@@ -58,8 +56,6 @@ 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