fix(cli/plugin): cli plugin target wasm32-wasip1

[genskyff]

Description:

Fixed the error where the target type behavior was inconsistent with the documentation when creating a plugin using CLI. Now wasm32-wasip1 can be used normally as a target.

❯ cargo run -p swc_cli_impl -- plugin new --target-type wasm32-wasip1 my-first-plugin
     Running `target\debug\swc.exe plugin new --target-type wasm32-wasip1 my-first-plugin`
✅ Successfully created my-first-plugin.
If you haven't, please ensure to add target via "rustup target add wasm32-wasip1"

BREAKING CHANGE:

Related issue (if exists):

• [Cli] Mismatch between documentation and CLI: wasm32-wasip1 vs wasm32-wasi target for plugin development #10284

[changeset-bot]

🦋 Changeset detected

Latest commit: af0e0ff

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[CLAassistant]

All committers have signed the CLA.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[codspeed-hq]

CodSpeed Performance Report

Merging #10293 will degrade performances by 1.05%

_{Comparing genskyff:fix/10284-cli-target-wasip1 (af0e0ff) with main (c276a38)}

Summary

⚡ 1 improvements
❌ 1 regressions
✅ 150 untouched benchmarks

⚠️ Please fix the performance issues or acknowledge them on CodSpeed.

Benchmarks breakdown

	Benchmark	BASE	HEAD	Change
❌	serialization of serde	2.8 µs	2.8 µs	-1.05%
⚡	es/lints/libs/terser	30 ms	29.3 ms	+2.46%