fix: resolve drive relative path

[sapphi-red]

Description

#8808 completely removed drive-relative path resolution behavior.
I removed this because I thought it was not intended: it was resolving using process.cwd() as a base, not the importer.

But I found that node.js supports drive-relative path resolution (nodejs/node#31710) and now I think this should be implemented.

This PR implements drive-relative path resolution (with the correct base). In addition, this PR adds absolute path resolution test.

Additional context

I tested the behavior of drive-relative path by:
$ node D:\foo.mjs on pwd = C:\

D:\foo.mjs

import '/bar.mjs'

console.log('foo.mjs')

D:\bar.js

console.log('bar.mjs')

---

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.

[netlify]

✅ Deploy Preview for vite-docs-main canceled.

Name	Link
🔨 Latest commit	841301d
🔍 Latest deploy log	https://app.netlify.com/sites/vite-docs-main/deploys/62cf7fe7994513000957fb34

[patak-dev]

@dominikg is this related to the issue you mentioned, would you confirm that this fix works for you?

[dominikg]

confirmed. Tested it in a local vm. Error happens with vite-3 from registry but not with a local build of this branch.