Migration of frontend tooling to Vite 4

[kloon15]

Description
This PR replaces the old build system with Vite 4, as a first step of #2623

🚨 Before submitting your PR, please read community, and indicate which issues (in any of the repos) are either fixed or closed by this PR. See GitHub Help: Closing issues using keywords.

• DO make sure you are requesting to pull a topic/feature/bugfix branch (right side). Don't request your master!
• DO make sure you are making a pull request against the master branch (left side). Also you should start your branch off our master.
• DO make sure that File Browser can be successfully built. See builds and development.
• DO make sure that related issues are opened in other repositories. I.e., the frontend, caddy plugins or the web page need to be updated accordingly.
• AVOID breaking the continuous integration build.

Further comments
Running it on my homeserver, currently everything seems to be working as before.

[ArthurMousatov]

I know this is closed, but I'm getting an error after this VITE PR:

This is after running "go run . --port 9000 --root ./demo_files/ --address 192.168.2.92"
I have run npm run watch on a separate terminal, and I seem to have a dist/public file afterwards:

Am I doing something wrong?

[kloon15]

As a part of improving the frontend development cycle without having to rebuild the js code, ur now expected to run a vite dev server alongside go and access the site from there:
npm run dev will start the vite dev server.
It will proxy api requests to localhost on port 8080.

[ArthurMousatov]

As a part of improving the frontend development cycle without having to rebuild the js code, ur now expected to run a vite dev server alongside go and access the site from there: npm run dev will start the vite dev server. It will proxy api requests to localhost on port 8080.

Awesome, that works. Thanks!