[Feature] add builder option to produces esbuild's metafile

[jkowalleck]

• I'd be willing to implement this feature (contributing guide)
• This feature is important to have in this repository; a contrib plugin wouldn't do

Describe the user story

As a plugin developer who uses @yarnpkg/builder@^4 to build the plugin I wrote, I want to have access to eslint's metafile, so that I can use it in additional tooling and analysis.

Describe the solution you'd like

Have a CLI switch, that enables eslint's metafile.
Something along builder build plugin --metafile.
The CLI switch would be "disabled" by default, meaning no file is written.
If the CLI switch is set to "true", then esbuild's metafile is written to bundles/${name}.meta.json.

Describe the drawbacks of your solution

This described solution would add a new optional CLI switch. If not used, it would not change any o current behaviors,
There should be no drawbacks with that, except that it keeps the current "vendor lock-in" with esbuild

Describe alternatives you've considered

I thought about having an option to pass basic esbuild config into the build command, which then is merged/overwritten by yarn specific settings, and the result is applied to esbuld.
The settings could be stored in the yarnrc file in a section called builder-build with a subsection per purpose (plugin or bundle).
This would open up a lot of custom options, true, but it would require people to learn the external structure and documentation and the whole exbild API - and be just not starter-friendly.
And most importantly, this all needs to work with possible custom injects into builder - which all is much too complicated for the small goal i had.