Upgrade from Laravel Mix to Vite

[betsyecastro]

• Requires Node.js v20
• Installs the Vite plugin and created the Vite configuration file.
• Includes adjustments to migrate from Webpack-style imports to ES module-compatible imports for Vite.
• Includes updated npm scripts and updated blade templates to use the @Vite directive instead of the old asset helper.

[betsyecastro]

@wunc Vite serves assets from a local dev server during development and only compiles them for production. CSS sourcemaps are a known limitation—the build.sourcemap option only generates JS sourcemaps, while CSS sourcemaps require the dev server. A plugin exists to generate CSS sourcemaps in builds, but it only supports Vite 5–6 (we're on 7) and is relatively new. The last two commits on this PR are the two approaches proposed:

Commit	b00287c	f7a6173
Vite version	7 (latest)	6 (downgrade)
Dependencies	"vite": "^7.2.2" "laravel-vite-plugin": "^2.0.1"	"vite": "^6.4.1" "laravel-vite-plugin": "^1.3.0" "vite-plugin-css-sourcemap": "^1.0.2"
CSS sourcemaps	Dev server only	Included in build
Workflow	Run dev server to debug CSS, then build for deploy	Single npm run build for everything
Trade-off	Stays current, extra step for CSS debugging	Matches previous Mix workflow, older dependencies

[wunc]

@betsyecastro thanks for the analysis. It's very helpful. Seeing this, I think I'd rather upgrade to the newer version (7) right now, and we'll adjust how we work in dev.