⏩ Use vite instead of Remix Classic Compiler (3)

[agoose77]

This PR works towards using Vite instead of the Remix Classic Compiler. From reading, it seems like only Vite supports changing the base path, which I think is a required solution to the v2 redirect problem (actually serve the theme from the base path it will be served from)

As this is an iterative PR, here are some findings:

• Switch to Vite configuration
• Split server and client loaders
• Drop LiveReload (Vite has HMR)

[agoose77]

This snapshot "works", but the static deployment is broken. I need to figure out the following:

• A sensible path to resolve ESM-CJS conflicts
• Why do we need to enable legacy routing when we opted in to v2 routing before the upgrade?
• Whether setting the base path works for static exports

This is all confusing stuff; there are so many interacting layers. But I think that's mainly a function of my knowledge rather than the problem at large.

[agoose77]

So it looks like the v1-v2 routing thing was maybe a fluke? I sat back down to the branch today and it broke the navigation.

Without that change, navigation and link-intent from non-index pages works, but the index seems to trigger a reload.

[agoose77]

Looks like the redirect phenomenon is actually @remix-run/react triggering a reload when it fails to dynamically import the route module. I set a breakpoint on that particular piece of logic in the browser.