fix(worker): prevent inject esm in classic workers

[bluwy]

Description

fix #11266
supersedes #12995

importAnalysis could run on classic worker code, which I think is the only non-ESM code we allow to be processed (?). This PR checks for classic workers and avoid adding top-level imports.

This should also fix the confusing errors from #5396 (does not fix the issue)

Additional context

The fix isn't really clean. I can't think of a way to inline __vite__injectQuery without a significant refactoring.

The test is also subpar but it somewhat works 😬

---

What is the purpose of this pull request?

• Bug fix
• New Feature
• Documentation update
• Other

Before submitting the PR, please make sure you do the following

• Read the Contributing Guidelines, especially the Pull Request Guidelines.
• Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
• Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
• Update the corresponding documentation if needed.
• Ideally, include relevant tests that fail without this PR but pass with it.

[bamtheboozle]

how exactly do we import a module as a "classic worker" and avoid vite injectquery?

[bluwy]

For classic workers, you can't use import in dev. You need to use importScripts instead. For imports to work in dev ootb, you can follow #10697