perf: remove redundant WASM tools installation from CI

The 'cargo install wasm-tools wac-cli wit-bindgen-cli' steps are no longer
needed because:

1. Bazel hermetic toolchain management automatically downloads and manages
   all required WASM tools through the wasm_tools_component_toolchain
2. Tools are cached and versioned through Bazel's repository system
3. This provides better reproducibility and faster CI runs
4. Eliminates ~2-3 minutes of tool compilation time per CI job

All WASM tools are now accessed through the WASM Tools Integration
Component, providing a unified interface while maintaining hermeticity.

Author: avrabe

.github/workflows/ci.yml

@@ -77,10 +77,6 @@ jobs:
           targets: wasm32-wasip1,wasm32-wasip2,wasm32-unknown-unknown
           components: clippy
 
-      - name: Install WASM tools
-        run: |
-          cargo install wasm-tools wac-cli wit-bindgen-cli
-
       - name: Verify Bazel Installation
         run: bazel version
 
@@ -235,7 +231,6 @@ jobs:
           curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh -s -- -y
           source ~/.cargo/env
           rustup target add wasm32-wasip2 wasm32-wasip1
-          cargo install wasm-tools wac-cli wit-bindgen-cli
 
       - name: Test Core Component Build
         run: |