fix: race condition creation module in graph in transformRequest

[patak-dev]

Description

Potential fix for #13030

Related to #8533

There could be a race condition if on the middle of processing a request, something changes in the environment (user code, optimized dep invalidation) that causes resolveId to return two different ids for the same URL.

We already had the module or the resolve result, and in loadAndTransform we were doing a new resolveId from the url after call load. This PR, avoids re-resolving by passing the resolved result if we already did it before load so we ensure the module node we add to the graph is the one we are currently transforming.

---

What is the purpose of this pull request?

• Bug fix
• New Feature
• Documentation update
• Other

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[patak-dev]

/ecosystem-ci run

[vite-ecosystem-ci]

📝 Ran ecosystem CI: Open

suite	result
astro	✅ success
histoire	✅ success
iles	✅ success
ladle	✅ success
laravel	✅ success
marko	✅ success
nuxt	❌ failure
previewjs	✅ success
qwik	✅ success
rakkas	✅ success
sveltekit	✅ success
vite-plugin-ssr	✅ success
vite-plugin-react	✅ success
vite-plugin-react-pages	✅ success
vite-plugin-react-swc	✅ success
vite-plugin-svelte	✅ success
vite-plugin-vue	✅ success
vite-setup-catalogue	✅ success
vitepress	✅ success
vitest	✅ success
windicss	✅ success