feat: rework dynamic-import-vars

[poyoho]

Description

fix: #6992

Additional context

I think we can deps on @rollup/dynamic-import-vars (dynamicImportToGlob) to re-implement it.

We can get some enhancements to dynamic import

• replace translater to es-module-lexer instead of compiler. There should be an improvement in performance?
• support dynamic import query syntax. such as ?raw.
• support @/${variable} resolve path.

Because we can make dynamic import use the code of import.meta.glob 🤔

---

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.n
• 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.

[caoxiemeihao]

Hey! 👋
It looks so cool!

[antfu]

#7537 got merged. While I do not completely understand this PR, from a brief overview, I guess maybe instead of depending on the glob transform directly, maybe we could directly transform the code to import.meta.glob expressions and let the importMetaGlob plugin handle the rest. Similiar to

vite/packages/vite/src/node/plugins/assetImportMetaUrl.ts

Lines 52 to 57 in 330e0a9

	s.overwrite(
	index,
	index + exp.length,
	`new URL((import.meta.glob(${pattern}, { eager: true, import: 'default' }))[${rawUrl}], self.location)`,
	{ contentOnly: true }
	)

[poyoho]

yes, this PR make the dynamicImport syntax to importGlob and now is easy to make it. 😊https://github.com/vitejs/vite/pull/7756/files#diff-309e5af7d3263d408c73cf68d3c7a2d526438f01ad6e1b56bf08c62d9cafa06dR101-R102