Clarify the distinction between plugins and builtins

[kmannislands]

Catching up on yarn modern, I've found it feels kinda arbitrary what's a plugin and what is built in. This has caused some confusion for my team.

I think this is best demonstrated by the example:

yarn workspace foo # built in
yarn workspaces foreach build # plugin

Okay, so workspaces is a plugin, makes sense. Yet:

yarn workspaces list # built in

I think the confusion here is exacerbated by the lack of separation in the docs.

I know there's a banner at the top of plugin doc pages telling you to install the plugin but I think this could be obviated by coming up with a more intuitive scheme for plugins/builtins and un-interleaving their respective docs.

Related Q, is there any list of useful yarn plugins out there? Something like esbuild's finding plugins section of docs or an awesome-yarn-plugins list would be very helpful.

[kmannislands]

In this specific example, I think it would make sense to combine workspaces list with the workspace tools plugin in the interest of adding --topological support to workspaces list. This feature would be quite useful for building bash scripts.