Match browser and Next.js handling of control characters in URL
schemes so obfuscated values like java\nscript:, java\rscript:,
java\tscript:, and leading-NUL forms are still recognized.
This keeps vinext's broader data:/vbscript: blocking while adopting
Next.js's character-by-character scheme matching for javascript:.
Also updates tests to cover embedded control characters and the parser
behavior for spaces and zero-width characters before the colon.
* chore: migrate to vite plus
* Disable typeAware and typeCheck
* Update CI
* Fix CI
* Fix test
* Clean
* Run test with vp
* Try revert
* react: false In test
* Fix test
* Revert "Try revert"
This reverts commit 009da10473.
* Update
* Update
* Try revert ci changes
* revert
* Run vp migrate
* Disable typeAware and typeCheck for now
* Better resolve for test
* Use vp dev instead of vite
* Update expect
* Fix NormalizeManifestModuleId
* Try increase timeout
* Update to use vp
* Try new check
* Bring back npx vp
* Migrate CI
* Make next-intl resolvable
* Update
* Update
* Update