[Bug?]: `yarn version <version>` doesn't work when the version jump isn't major/minor/patch/prerelease/decline

Self-service

• I’d be willing to implement a fix

Describe the bug

See title and the reproduction below.

Originally reported by @vefydwy in #3278.

To reproduce

await packageJsonAndInstall({
  version: `0.0.0`,
});

await expect(yarn(`version`, `2.0.0`))
  .resolves.toBeTruthy();

Environment

  System:
    OS: Linux 5.13 Arch Linux
    CPU: (32) x64 AMD Ryzen 9 5950X 16-Core Processor
  Binaries:
    Node: 16.0.0 - /tmp/xfs-049440fa/node
    Yarn: 3.0.1.dev - /tmp/xfs-049440fa/yarn
    npm: 7.10.0 - ~/.nvm/versions/node/v16.0.0/bin/npm

Additional context

Broken by https://github.com/yarnpkg/berry/pull/3158.

[arcanis]

• set version latest downloads the latest stable >2 if the current release you use is already >2, otherwise the latest 1.x (in other words it doesn’t silently upgrade past 1.x, for backward compatibility)

• set version berry always downloads the latest stable version >2 (including by upgrading to higher majors)

• set version canary (new in 3.0) always downloads the latest release candidate.

The difference between stable and rc is very small - it’s almost more a marketing difference than functional one, as all the tests need to pass whether it’s one or the other. At Datadog we even use builds built straight from sources, for example.

[merceyz]

It’s available in the latest canary builds

yarn set version canary && yarn plugin import version