Vite: Use Vite 3 (temporarily)

[IanVS]

Issue:

What I did

This implements option D from https://www.notion.so/chromatic-ui/Vite4-support-c986d1e531e34ec7b70b72f4698c0328.

Pseudo-Vite4 support with Vite3

It’s possible that we can support Vite4 projects with Vite3 under the hood temporarily. This would support Vite3 users in the short term, and if we could make it work for Vite4 users it would be the best temporary option since it works today. We’d want to replace this method before the RC.

Blocker: Do users’ Vite4 plugins work with Vite3? IanVS is investigating.

I did this by returning our vite version range to only encompass version 3, so Storybook will continue to use vite 3 for now, but users can upgrade their apps to vite 4 without issue. This should work so long as the newer framework plugins that those users put into their vite.config.js files don't cause problems in vite 3. I tested react locally, and storybook's vite 3 worked fine with the newer @vitejs/plugin-react intended for use with vite 4. I'm not positive all plugins will work that way, but hopefully CI will suss that out, since the repros are using the newer vite + plugins.

I've also forced the older version of the react plugin to be used for mdx processing, removed the react plugin from non-react frameworks, and re-enabled the story disabled in #20210.

How to test

I'm hopeful CI will be instructive here. You could also create a sandbox and try out different versions of packages, but you may need to use --no-link because of version mismatches with the repros.

[IanVS]

Previously, though I'm not sure why, react fast-refresh was not being added to mdx files. With my first attempts in this PR it was, which was causing problems. I've disabled fast-refresh for mdx files (which @joshwooding can confirm, but I don't think ever worked previously anyway), and I'm hopeful that this will work, but I need to get in bed before CI finishes.

[JReinhold]

Great quick work! 💪

LGTM if CI passes.