feat(builder): build plugins with esbuild

[paul-soporan]

What's the problem this PR addresses?

We currently use ESBuild to build the bundle and Webpack to build the plugins.

How did you fix it?

Plugins will now also be built using ESBuild. I kept the dynamic lib magic by creating an inline plugin. I also kept the wrapper by using banner and footer.

Stats for compiling @yarnpkg/plugin-workspace-tools:

Before:

• Time: 17s 177ms
• Bundle Size: 47.53 KB

After:

• Time: 3s 911ms
• Bundle Size: 48.73 KB (very small increase, part of it because of the new //prettier-ignore comment in the wrapper)

Note: I think building plugin-version might be a bit broken currently because of how @yarnpkg/esbuild-plugin-pnp handles optional peer deps, but I'll investigate tomorrow after getting some sleep.

Checklist

• I have read the Contributing Guide.

• I have set the packages that need to be released for my changes to be effective.

• I will check that all automated PR checks pass before the PR gets reviewed.

[paul-soporan]

I decided to make @yarnpkg/esbuild-plugin-pnp downgrade errors to warnings on dynamic resolve calls until evanw/esbuild#1127 is addresed so that this PR can be unblocked.

[paul-soporan]

Waiting on #2863.

[merceyz]

I don't see why the cli needs a release 🤔

[paul-soporan]

I bumped it because updating ESBuild might cause the generated bundle to be different 🤔

[merceyz]

Oh yeah, due to esbuild not always including __esModule anymore it might break plugins that depends on it existing 🤔

[arcanis]

LGTM - wdyt, @merceyz?

[merceyz]

I'm a bit worried about #2717 (comment) but otherwise LGTM