ci: remove serde_core/wasm32v1-none workarounds, re-enable 35+ disabled jobs

The serde_core + Rust 1.88 issue only affects wasm32v1-none target.
wasm32-unknown-unknown works fine, and wasm-builder falls back to it
automatically when wasm32v1-none is not installed.

- Remove all `rustup target add wasm32v1-none` steps (12 files)
- Remove SKIP_WASM_BUILD=1 env vars added as workaround (28 occurrences)
- Re-enable quick-benchmarks job (tests.yml)
- Re-enable check-core-crypto-features job (checks.yml)
- Re-enable 15 build/zombienet jobs (build-publish-images.yml)
- Re-enable test-pezframe-examples-compile-to-wasm and
  test-deterministic-wasm jobs (tests-misc.yml)

Tracking: #355, #357, #358
Upstream: https://github.com/serde-rs/serde/issues/3021 (still open)

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

@@ -34,9 +34,6 @@ jobs:
       # -Cinstrument-coverage slows everything down but it is necessary for code coverage
       # https://doc.rust-lang.org/rustc/instrument-coverage.html
       RUSTFLAGS: "-Cdebug-assertions=y -Dwarnings -Cinstrument-coverage"
-      # Temporary: Skip WASM build due to serde_core + Rust 1.88 + WASM bug
-      # Tracking: https://github.com/pezkuwichain/pezkuwi-sdk/issues/358
-      SKIP_WASM_BUILD: 1
       LLVM_PROFILE_FILE: "/__w/pezkuwi-sdk/pezkuwi-sdk/target/coverage/cargo-test-${{ matrix.ci_node_index }}-%p-%m.profraw"
     strategy:
       fail-fast: false