Tech: make the version range of vite also allow for vite 4

[ndelangen]

Issue: support vite 4?

What I did

I allowed vite in the version range, this fixes yarn start. (in our contribution.md)
It might also just be the right thing to do?

[IanVS]

It looks like this is an alternate solution to #20281? Is there a reason not to go the route I took there? I'd prefer to keep vite as a peer dependency, as it was in 6.5, and I think we can do it without problem now that we are not injecting the react plugin to handle mdx.

[ndelangen]

No there isn't. @JReinhold asked me to look into his svelte PR, and when I did I noticed the yarn failure, so I fixed it, and extracted the fix out into it's own PR here.

[ndelangen]

@IanVS I do not know what's going on with that PR, I'm happy to prefer that one over this one, for sure.
But I'd love to have yarn start and vite sandboxes in general work without linking, which is all I wanted to achieve in this PR.

[ndelangen]

I can't reproduce this unit-test fail locally. Argh I feel like giving up on this.

[IanVS]

I found the issue in the other PR(#20281). react-docgen wasn't being pinned correctly.

[ndelangen]

ok, I'll close it again