chore: use JSDoc type imports in more files

[damianstasik]

This PR continues the work started by Rich in #12130. I've tried to include only files that don't have any PRs open against them. One note: to avoid excessive line width, I've switched to a namespace import when there are more than five type imports from a single module. It's an arbitrary limit, but I'm happy to adjust the PR if needed.

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
• Prefix your PR title with feat:, fix:, chore:, or docs:.
• This message body should clearly illustrate what problems it solves.
• Ideally, include a test that fails without this PR but passes with it.

Tests and linting

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

[changeset-bot]

⚠️ No Changeset found

Latest commit: edbb6a4

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

[Rich-Harris]

thank you! it turns out this exposes some existing fault lines (hence the test failures) which i'll address in a separate PR first

[Rich-Harris]

#12255 fixes the CompileError stuff

[Rich-Harris]

It seems that * as imports that make their way into the generated public types bundle don't work, for whatever reason, so I replaced those with named specifiers