chore(deps): bump vite-plus to 0.1.21-alpha.6

[fengmk2]

Summary

Bump vite-plus and related packages to alpha 0.1.21-alpha.6.

Updated where applicable:

• vite-plus
• vitest (alias to @voidzero-dev/vite-plus-test)
• vite (alias to @voidzero-dev/vite-plus-core)
• overrides / resolutions / pnpm.overrides / pnpm-workspace.yaml catalogs

Test plan

• CI passes

[gemini-code-assist]

Code Review

This pull request updates the versions of vite, vite-plus, and vitest to 0.1.21-alpha.6 across multiple package.json files in the repository. The reviewer suggests adopting pnpm's catalog: protocol to centralize version management for these dependencies, which would simplify future updates and ensure consistency across the workspace.

[gemini-code-assist]

Since the PR description mentions updating pnpm-workspace.yaml catalogs, consider using the catalog: protocol for these dependencies. This would centralize version management for vite, vite-plus, and vitest, avoiding the need to manually update multiple package.json files across the repository for each release.

Suggested change

	"vite": "npm:@voidzero-dev/vite-plus-core@0.1.21-alpha.6",
	"vite-plugin-mkcert": "^1.17.10",
	"vite-plus": "0.1.20",
	"vitest": "npm:@voidzero-dev/vite-plus-test@0.1.20"
	"vite-plus": "0.1.21-alpha.6",
	"vitest": "npm:@voidzero-dev/vite-plus-test@0.1.21-alpha.6"
	"vite": "catalog:",
	"vite-plugin-mkcert": "^1.17.10",
	"vite-plus": "catalog:",
	"vitest": "catalog:"

[gemini-code-assist]

The overrides section can also leverage pnpm catalogs to ensure version consistency across the entire workspace without hardcoding the alpha version in every package.

Suggested change

	"vite": "npm:@voidzero-dev/vite-plus-core@0.1.21-alpha.6",
	"vitest": "npm:@voidzero-dev/vite-plus-test@0.1.21-alpha.6"
	"vite": "catalog:",
	"vitest": "catalog:"