fix(scanner): catch all external files for glob imports

[XiSenao]

Description

fixes #15281
fixes #15284
refs #15140

Starting from esbuild@0.19.0, it will attempt to bundle glob imports modules, and the special point in handling glob import modules is to skip calling the onResolve hook and directly call the onLoad hook. If the module cannot be captured by the existing onLoad hook, then it will prompt "No loader is configured for ".xxx” files:", which is a common issue encountered in vite@5.0.0 and later versions.

Due to the inability of esbuild to call onResolve plugin when parsing glob imports, vite relies on esbuild during the initial pre-build phase to quickly scan the pre-built dependencies. The modification of #15140 only supports the suffixes supported by Vite. There is no additional processing for suffixes not supported by Vite, so import unsupported suffix types during the pre-build phase will result in an error when scanning dependencies. This change will handle all unconsidered suffixes as a fallback, preventing vite from throwing errors when scanning new suffixes during the pre-build phase.

---

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, especially the Pull Request Guidelines.
• 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).
• Update the corresponding documentation if needed.
• Ideally, include relevant tests that fail without this PR but pass with it.

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[sapphi-red]

I wonder if we should revert #15140 and just add the following code at the end? What do you think?

// onResolve is not called for glob imports.
// we need to add that here as well until esbuild calls onResolve for glob imports.
// https://github.com/evanw/esbuild/issues/3317
build.onLoad({ filter: '.', namespace: 'file' }, () => {
  const externalOnLoadResult: OnLoadResult = {
    loader: 'js',
    contents: 'export default {}',
  }
  return externalOnLoadResult
})

[XiSenao]

In the setupExternalize function in #15140, I think it can be kept to serve as a functional prompt. I think that placing the build.onLoad hook contained within it at the end for fallback processing would suffice. Do you think so? @sapphi-red

[XiSenao]

It seems that the test has returned to normal 🤔

[sapphi-red]

Thanks! LGTM

[XiSenao]

What else needs to be considered for the current changes? @patak-dev

[patak-dev]

Thanks for all your work in Vite lately @XiSenao!