chore: update dependencies

[dominikg]

update dependencies

Notes:
typescript 4.5 is available but updated to ~4.4.4 (4.5 introduces .d.mts files that cause test failures, needs investigation)
esbuild 0.14 available but updated to 0.13.15 (avoid breaking changes)

Major updates for marked and mime in kit package.

No changesets added, do we require them for minor esbuild updates (may affect adapter builds?)

It looks like vite is going to stick with typescript 4.4/esbuild 0.13 for the upcoming 2.7 release and updates them in 2.8 afterwards.
We should do a concerted update to ts 4.5/esbuild 0.14/vite 2.8 once that has happened.

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

• It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
• This message body should clearly illustrate what problems it solves.
• Ideally, include a test that fails without this PR but passes with it.

Tests

• Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

• If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpx changeset and following the prompts. All changesets should be patch until SvelteKit 1.0

[changeset-bot]

🦋 Changeset detected

Latest commit: 9832709

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 8 packages

Name	Type
@sveltejs/adapter-cloudflare	Patch
@sveltejs/adapter-cloudflare-workers	Patch
@sveltejs/adapter-netlify	Patch
@sveltejs/adapter-node	Patch
@sveltejs/adapter-static	Patch
@sveltejs/adapter-vercel	Patch
create-svelte	Patch
@sveltejs/kit	Patch

Not sure what this means? Click here to learn what changesets are.

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

[benmccann]

probably not a bad idea to have a changeset just to be safe. I'd rather err towards mentioning something in the changelog than not

[dominikg]

probably not a bad idea to have a changeset just to be safe. I'd rather err towards mentioning something in the changelog than not

done.