fix(hmr): handle virtual module update

[bluwy]

Description

Alternative to #10313
Should also fix #6871 but I'm not sure how to test it

This PR ensures HMR urls are properly wrapped before sending to the HMR client.

Additional context

---

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.

[patak-dev]

Thanks! I was going to propose the same in the other PR.

[patak-dev]

/ecosystem-ci run

[vite-ecosystem-ci]

📝 Ran ecosystem CI: Open

suite	result
astro	✅ success
iles	✅ success
ladle	❌ failure
laravel	❌ failure
marko	✅ success
nuxt-framework	✅ success
rakkas	✅ success
storybook	❌ failure
svelte	✅ success
vite-plugin-ssr	❌ failure
vite-setup-catalogue	✅ success
vitepress	❌ failure
vitest	❌ failure
windicss	✅ success

[patak-dev]

The failures in ecosystem-ci seem related to the current issues in the 3.2 ci (most of them are problems with the project's CIs).
Let's merge this one for 3.2. @bluwy maybe you could backport this in a PR to v3.1 and we can run /ecosystem-ci run there too? We need to work with maintainers to get back to a green state for ecosystem ci, it is quite hard to use it with so many false positives (dominikg is also working on an update that will run the project's CI without overrides after a fail so we can mark results as invalid instead of a fail)