fix: fix re-mocking virtual module

[hi-ogawa]

Description

• Closes Virtual module mocking issue in Vitest 4 #9742

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. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
• Ideally, include a test that fails without this PR but passes with it.
• Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.
• Please check Allow edits by maintainers to make review process faster. Note that this option is not available for repositories that are owned by Github organizations.

Tests

• Run the tests with pnpm test:ci.

Documentation

• If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

• Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.

[netlify]

✅ Deploy Preview for vitest-dev ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	52d07fe
🔍 Latest deploy log	https://app.netlify.com/projects/vitest-dev/deploys/699fcab22291450008f6855a
😎 Deploy Preview	https://deploy-preview-9748--vitest-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[hi-ogawa]

For the case of virtual module, here we previously had id = /@id/virtual-module (aka "url") as module runner fetchModule result, which then leaded to evaluatedModuleNode.id = mock:/@id/virtual-module during later mock interception.

However, when invalidating mock for next doMock calls, we use resolveId of virtual-module and it tries to invalidate mock:virtual-module. This inconsistency makes invalidation to miss.

What this resolvedMock case should do instead is to return id as resolvedId of mocked module, which is already available as resolvedMock.id, so that is the solution here.