rust: split out wasm32-wasip1 std support

[burak-ok]

Package the wasm32-wasip1 target as a rust-std-wasm32-wasip1 subpackage, install it without installer metadata bleed, and ship the corresponding wasi-libc license notices.

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

• The toolchain has been rebuilt successfully (or no changes were made to it)
• The toolchain/worker package manifests are up-to-date
• Any updated packages successfully build (or no packages were changed)
• Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
• Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
• All package sources are available
• cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
• LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
• All source files have up-to-date hashes in the *.signatures.json files
• sudo make go-tidy-all and sudo make go-test-coverage pass
• Documentation has been updated to match any changes to the build system
• Ready to merge

---

Summary

This PR adds wasm32-wasip1 target suport to Azure Linux's rust package, so Rust-based WASI workloads can build with the distro-provided Rust toolchain. For that it introduces a new rust-std-wasm32-wasip1 subpackage

Change Log

• Add wasm32-wasip1 target support to rust with a new rust-std-wasm32-wasip1 subpackage and the required WASI source/signature/license updates

Does this affect the toolchain?

NO

Test Methodology

Locally built the packages and used the package to build the Inspektor Gadget builder which compiles Rust to WASM