Upgrade to Vite 3.2

[benmccann]

I wasn't sure if I should include a changeset and didn't for now. This mostly affects tests. create-svelte does use a newer version, but you'd have already gotten the latest upon using npm install previously, so I'm not sure there's really a user-visible change here

[changeset-bot]

⚠️ No Changeset found

Latest commit: d2e96d2

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[Conduitry]

Does 3.2 provide any new features we're going to want to make use of? Before we hit SvelteKit 1.0 is the time to be doing any bumping of peerdeps.

[benmccann]

There's not much in 3.2 that affects us. Only thing I see in the changelog is vitejs/vite#9970, which is a bug fix for #1042

[dominikg]

just triggered a rerun of tests on #7355 that should go in first otherwise it gets breaking changes from this here. ofc. we can also just redo it after, but would rather not

[benmccann]

We can't merge this anyway. lint is failing because of vitejs/vite#10656

[dominikg]

someone mentioned adding types/picomatch to devDependencies as a workaround. We can either do that or wait until fixed in vite. Also checking if we can enable out lint in ecosystem-ci to catch these earlier.

[dominikg]

fix has already been merged in vite, so better to wait here and bump to 3.2.1

[Rich-Harris]

i bumped esbuild across the board so that we don't end up with two versions in the lockfile

[benmccann]

Sounds good