[Feature] Earlier dependency cycles check in `foreach`

Describe the user story

I'm publishing the Yarn packages, and I noticed that the publishing aborted midway because of a (valid) dependency cycle between plugin-node-modules and yarnpkg-cli (some deps in the plugin should have been peer deps). It's not ideal, because it means that the releases may be half-published.

Describe the solution you'd like

The yarn workspaces foreach command should make a first quick sanity check to ensure that there is no dependency cycle given the command arguments.

Describe the drawbacks of your solution

It adds a bit of delay before the commands run, but I think it's acceptable to assume that foreach will be somewhat slow anyway.

Start by locating the implementation of the Yarn workspaces foreach command and reading how its command arguments determine the workspace set and dependency graph. Add a preflight cycle check that runs before any foreach commands execute; done means a cycle is rejected early rather than allowing a partial publish.