[1.1] Fix dependency issue with Vite 5

[jessarcher]

This PR fixes the following dependency resolution issue for users of Vite 5 by allowing it to be a peer dependency in the latest version of this plugin.

npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: undefined@undefined
npm error Found: [email protected]
npm error node_modules/vite
npm error   dev vite@"^5.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer vite@"^6.0.0" from [email protected]
npm error node_modules/laravel-vite-plugin
npm error   dev laravel-vite-plugin@"^1.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.

Our understanding was that NPM would not attempt to install/upgrade this plugin to v1.1 and instead continue to use v1.0 until the project's Vite dependency was bumped to v6. However, it seems that NPM tries to install the latest versions purely based on the constraints in package.json and then fails if they're incompatible instead of using the latest mutually compatible versions as Composer does.

It would seem that with NPM, the only way to safely drop support for a peer dependency major version is with a major version release, so we've decided to reintroduce support for Vite 5, which matches official Vite plugins like @vitejs/plugin-vue.

Fixes #311
Fixes #312

[kylemilloy]

You guys are rockstars. Thanks for the late night fix 💪👁️👄👁️💪