Refactors yarn workspaces foreach

[arcanis]

What's the problem this PR addresses?

The command default's behavior was "worktree" (ie to only run on the current workspace and whatever it listed in its own workspaces field), but it was rarely what users expected (since very few people use nested workspace setups).

How did you fix it?

The main functional change is that one of --all, --worktree, --since, or --recursive is now required. The --since flag doesn't automatically imply --worktree anymore.

Using --all with one of --worktree, --from, --since, or --recursive doesn't work anymore, since they have incompatible meanings (it still accept --include and --exclude to further refine the list).

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.

[belgattitude]

@arcanis note sure about --from.

Since rc49, the following is breaking

yarn workspaces foreach -tv --from 'examples/*' run typecheck

With

Usage Error: Invalid option schema: missing at least one property from "all", "recursive", "since", or "worktree"

Is it intended ?

Link: belgattitude/shared-dx#324

[GauBen]

Hey there, --all is still marked as the default flag in the documentation despite this change