feat(wasm-ci): make rustup target install configurable via wasm-target-install input

[BimaPangestu28]

Summary

The wasm job's rustup target install was hardcoded to wasm32-wasip2, but the surrounding cargo args (wasm-check-args, wasm-build-args, wasm-validate-glob) are all input-controllable. Callers that override the target on those args still picked up the wasip2 toolchain — the build then failed with E0463: can't find crate for \core` because cargo \--target` requested a target the toolchain didn't install.

This adds a wasm-target-install input on both pr-ci.yml and the parent reusable wasm-component-ci.yml, defaulting to wasm32-wasip2 so every existing caller keeps working unchanged.

Why now

greentic-biz/greentic-bundle-extensions#26 is taking up the cards2pack-core empty-routing fix from greenticai/greentic-bundle#95. After bumping cards2pack-core and bundle-standard-core to 1.2.0-dev.25512130996, the dep tree pulls in:

bundle-standard-core 1.2.x → zip ^8 → typed-path ^0.12

typed-path 0.12.x uses feature(wasip2) stdlib APIs that aren't stable on wasm32-wasip2 under Rust stable:

error[E0658]: use of unstable library feature `wasip2`
  --> typed-path-0.12.3/src/lib.rs:3:57

The same crate compiles cleanly on wasm32-wasip1, and cargo-component already produces a Component Model artifact on wasip1 that wasmtime loads via the runtime's Component Model wrapper. reference-extensions/bundle-standard/build.sh has always emitted to wasm32-wasip1 — the CI/build mismatch only surfaced after this dep upgrade. PR #26 needs to set wasm-target-install: wasm32-wasip1 to align CI with the production build path.

What changed

• .github/workflows/pr-ci.yml:
  • New input wasm-target-install (default wasm32-wasip2)
  • Replace hardcoded targets: wasm32-wasip2 (wasm job rustup install) with targets: ${{ inputs.wasm-target-install }}
• .github/workflows/wasm-component-ci.yml:
  • Mirror the new input + thread it down to the pr-ci.yml call

Backward compatibility

Default value is wasm32-wasip2, so every existing caller — and every other reusable-workflow consumer in the org — gets identical behavior. Only callers that explicitly opt in via wasm-target-install: ... change their target install.

Test plan

• YAML syntax check (python3 -c "import yaml; yaml.safe_load(...)")
• After merge: rerun greentic-biz/greentic-bundle-extensions#26 CI — wasm job should pass with the wasip1 input override
• Sanity sweep across other reusable-workflow consumers in the org — each should continue to install wasip2 unchanged (default preserved)

[BimaPangestu28]

Superseded by greenticai/greentic-bundle#96, which pins zip = "=7.1.0" to remove the transitive typed-path 0.12.x dependency at the source.

After #96 merges and stamps a new dev-publish version, greentic-biz/greentic-bundle-extensions#26 will re-pin to that version and drop its wasm32-wasip1 override — wasm32-wasip2 (the org-wide default) builds cleanly on stable Rust once the typed-path dep is gone.

No infrastructure change needed in this repo. Closing without merging.