[feature] Allow opting out of the `yarnPath` for the yarn package manager

[latin-1]

[feature] Allow opting out of the `yarnPath` for the yarn package manager

[milesj]

@latin-1 I'm not sure if we can handle this on our end? We don't explicitly set that yarnPath field. We just call yarn commands that in turn do it.

[latin-1]

@milesj I'm not sure why moon does not use proto to manage yarn versions.

For yarn 4, yarn set version will generate yarnPath if 1. corepack is not global enabled, or 2. --no-yarn-path is specified. Yarn 2/3 will always write it.

Using yarn set verion programmingly might not be a good idea IMHO.

[milesj]

yarn is managed by proto via moon, but the yarn set version stuff predates it. Probably best to just remove it at this point.

[milesj]

Will be in 1.27