fix(importMetaGlob): handle alias that starts with hash

[bluwy]

Description

fix #17614
ref #12467

The importMetaGlob logic always assumed globs that starts with # are subpath imports, and so the resolved path is relative and should join to the root. However, aliases that starts with # could resolve too, which returns an absolute path.

Due to the previous assumption, the root and absolute path was joined, causing an invalid path for globbing.

This PR fixes it by returning the subpath imports resolved path as absolute instead, preventing the need for any special handling. This means the pre + globSafeResolvedPath(resolved, glob) part also gets executed for subpath imports, which I think it's more correct and handles the edge cases there.

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[patak-dev]

/ecosystem-ci run

[vite-ecosystem-ci]

📝 Ran ecosystem CI on 052a18c: Open

suite	result	latest scheduled
astro	❌ failure	❌ failure
nuxt	❌ failure	❌ failure
sveltekit	✅ success	❌ failure
vike	❌ failure	❌ failure
vite-plugin-react-pages	❌ failure	❌ failure
vitest	❌ failure	❌ failure

✅ analogjs, histoire, ladle, laravel, marko, previewjs, quasar, qwik, rakkas, remix, unocss, vite-plugin-pwa, vite-plugin-react, vite-plugin-react-swc, vite-plugin-svelte, vite-plugin-vue, vite-setup-catalogue, vitepress