Fix aliased plugin imports in v1 migration

[fallintoplace]

Summary

• preserve the local alias when migrating pluginified imports from @tauri-apps/api
• update the v1 migration fixtures to expect valid namespace imports
• reparse migrated JS, Svelte, and Vue output in tests so invalid syntax is caught

Root cause

The migrator generated aliased namespace imports as import * as cli as superCli from "...", which is not valid ESM and breaks migrated code for inputs like import { cli as superCli } from "@tauri-apps/api".

Testing

• cargo test -p tauri-cli 'migrate::migrations::v1::frontend::tests::migrates'

[github-actions]

Package Changes Through 51f23f9

There are 5 changes which include tauri-utils with patch, tauri-bundler with patch, tauri with patch, tauri-cli with patch, @tauri-apps/cli with patch

Planned Package Versions

The following package releases are the planned based on the context of changes in this pull request.

package	current	next
tauri-utils	2.9.2	2.9.3
tauri-bundler	2.9.2	2.9.3
tauri-runtime	2.11.2	2.11.3
tauri-runtime-wry	2.11.2	2.11.3
tauri-codegen	2.6.2	2.6.3
tauri-macros	2.6.2	2.6.3
tauri-plugin	2.6.2	2.6.3
tauri-build	2.6.2	2.6.3
tauri	2.11.2	2.11.3
@tauri-apps/cli	2.11.2	2.11.3
tauri-cli	2.11.2	2.11.3

Add another change file through the GitHub UI by following this link.

---

Read about change files or the docs at github.com/jbolda/covector

[Legend-Master]

Thanks! Could you also add a change file?

https://github.com/tauri-apps/tauri/blob/dev/.changes/README.md

Also you'll need to sign your commits for me to merge this

https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits

[Legend-Master]

Thanks!