fix(optimizer): log esbuild error when scanning deps

[fi3ework]

Description

from #11966
The error message thrown from esbuild in the scanning stage now is quite opaque. This PR added essential error messages and stack traces.

log before:

log now:

Additional context

---

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.

[bluwy]

I tested this locally but it seemed the message is still a bit intertwined, since it logs and errors at the same time. I went in and updated the log error 😬 It should look like this now:

Let me know if this works for you. There's two new lines under esbuild frames, but I'm leaving it as-is to not mess with esbuild's formatted messages in case it changes.

[fi3ework]

The only thing I am concerned about is the stack is not completed. It lost the stack sections in the image below which I added by composing a new Error() which may result in the log being a bit ugly. 😬

[bluwy]

I removed that as I'm not sure if it's important. We need to have the esbuild stacktrace too so they know it's coming from esbuild. Between the two frames, I think keeping esbuild's one is enough. The user can search for "Failed to scan dependencies from entries" in Vite's code if they want to know where this error is emitted.

[fi3ework]

LGTM, nice polishing.