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/check-getting-started.yml

@@ -74,8 +74,6 @@ jobs:
     env:
       # Use local templates from the repo instead of cloning from external repos
       PEZKUWI_TEMPLATE_SOURCE: ${{ github.workspace }}/templates
-      # Skip WASM build due to serde_core compatibility issues
-      SKIP_WASM_BUILD: 1
       # Fix HOME directory mismatch in containers (rustup requires this)
       HOME: /root
     steps:
@@ -212,8 +210,6 @@ jobs:
     env:
       # Use local templates from the repo instead of cloning from external repos
       PEZKUWI_TEMPLATE_SOURCE: ${{ github.workspace }}/templates
-      # Skip WASM build due to serde_core compatibility issues
-      SKIP_WASM_BUILD: 1
     steps:
       - name: Checkout
         uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8 # v5.0.0