fix: call tryFsResolve for relative new URL(foo, import.meta.url)

[sapphi-red]

Description

new URL('./path-without-extension', import.meta.url) was supported in past but wasn't working since 4.3. This was caused by #12450.

fixes #13141

refs #7837

Additional context

I wonder if we should remove these resolvings from new URL(foo, import.meta.url) (i.e. only support relative paths with extensions) as new URL is a constructor that simply resolves relative paths. Instead to introduce import.meta.resolve for that usage as import.meta.resolve will resolve like node and it works with Node.

---

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 PR Title 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.

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[patak-dev]

/ecosystem-ci run

[vite-ecosystem-ci]

📝 Ran ecosystem CI: Open

suite	result
astro	❌ failure
histoire	✅ success
iles	✅ success
ladle	✅ success
laravel	✅ success
marko	✅ success
nuxt	❌ failure
previewjs	✅ success
qwik	✅ success
rakkas	✅ success
sveltekit	✅ success
unocss	✅ 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

[patak-dev]

I wonder if we should remove these resolvings from new URL(foo, import.meta.url) (i.e. only support relative paths with extensions) as new URL is a constructor that simply resolves relative paths. Instead to introduce import.meta.resolve for that usage as import.meta.resolve will resolve like node and it works with Node.

Given that this was working in 4.2, I think it is a good idea to move forward with your PR. We can discuss the breaking change for Vite 5, but I think we may need to keep supporting this. import.meta.resolve looks like a good tool to have though.

[patak-dev]

Nuxt and Astro are also failing in main