[v12] Replace Webpack with Vite

[ryanclark]

Backport Vite to v12

Original PR - #21168
Includes changes from

• Fix styled-components CSS prop in Storybook #23427
• Fix vite development for desktop websocket endpoint #23815
• Vite fixes (default exports, circular dependency) #24591
• Add the favicon back #24904
• Move the favicon so Teleport serves the static file #26084
• Fix vite config #25514

[ravicious]

Why is this needed on v12 and not on master?

[ryanclark]

On master/v13, the dependencies for swc are set in yarn.lock to the versions that work. If I don't pin this, we get an incompatible @swc/core package and the build errors.

[ravicious]

I see that master uses @vitejs/plugin-react-swc ^3.2.0 vs ^3.3.1 on this branch. I managed to massage yarn.lock into resolving @swc/core to 1.3.36 (a1bfb9f) by doing this:

1. Remove @vitejs/plugin-react-swc from package json.
2. Run yarn.
3. Add it back to package.json with "@vitejs/plugin-react-swc": "~3.2.0" (this won't upgrade it past 3.2.x).
4. Run yarn.
5. Remove @swc/core resolution.

What do you think about about restricting plugin-react-swc to ~3.2.0 instead of adding that @swc/core resolution? I care about this only because adding a resolution is a pretty heavy-handed hammer that I think we should use only as a last resort.

[ravicious]

It looks like the changes here cause some type errors to pop up in web/packages/teleterm. I wonder why it's the case on v12 and not on v13/master. 🤔

[ryanclark]

I'll take a look

[zmb3]

@ryanclark I'm going to close this one - it hasn't been touched in 4 months and eventually v12 will die out.

[ryanclark]

@ryanclark I'm going to close this one - it hasn't been touched in 4 months and eventually v12 will die out.

Yeah fair enough. I didn't pick it back up as it seemed v12 wasn't going to be supported for much longer, I just forgot to close it