fix: handle local and module scripts separately

[benmccann]

Description

Treat Svelte's <script> and <script context="module"> as separate contexts during import scan

Fixes #5446

Additional context

This is a very annoying issue that causes prebundling to fail so that the server won't start if you use variables with the same name in different script contexts, which is a very common thing to do in Svelte

---

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.
• Read the Pull Request Guidelines and follow the Commit Convention.
• 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).
• Ideally, include relevant tests that fail without this PR but pass with it.

[yyx990803]

I realize this could technically happen in .vue files as well, when a user uses variables with the same name in both normal <script> and <script setup> (although this seems less common than in Svelte? I personally have never seen anyone do this)

So I think some level of hard-coding for this is unavoidable (before the refactor), but on a high level there would be two code paths:

1. "Module" context script tags: <script> in vue, and <script context="moule"> in svelte.
2. "Local" context script tags: <script setup> in vue, and <script> in svelte.

We should detect these two paths upfront and then apply the new virtual module logic to (2). This would allow us to limit the framework-specific part to the script context detection phase and make the virtual module handling framework agnostic.

[benmccann]

I'm not sure I understood 100% of that comment, but I did add support for .vue files as suggested

done