Statically analyse exports v2

[dummdidumm]

WIP alternative to #13669, with a few differences

• static analysis happens as part of the transform hook. That means we don't need acorn/acorn-ts. It's a tiny bit more hacky that way though since we mutate the manifest after its creation. If we wanna be pure we do the analysis as part of generating the manifest, and then we would need acorn/acorn-ts. I also didn't find a good way yet to influence the dev manifest (probably more hacky mutation needed there)
• static analysis is all-or-nothing: if one of the exports cannot be statically analysed, the whole thing returns null and as such the whole thing falls back to dynamic loading. With this we can avoid the proxy and avoid making all export values be promises, which in turn means less code paths are touched

---

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 pnpm changeset and following the prompts. Changesets that add features should be minor and those that fix bugs should be patch. Please prefix changeset messages with feat:, fix:, or chore:.

Edits

• Please ensure that 'Allow edits from maintainers' is checked. PRs without this option may be closed.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 2027c7d

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

[svelte-docs-bot]

Preview: https://svelte-dev-git-preview-kit-13673-svelte.vercel.app/