feat(cli): update set-version to match new release structure, add --tag, --commit

[alvrs]

• updates the set-version cli command to work with the new release structure by adding two new options:
  • --tag: install the latest version of the given tag. For snapshot releases tags correspond to the branch name, commits to main result in an automatic snapshot release, so --tag main is equivalent to what used to be -v canary
  • --commit: install a version based on a given commit hash. Since commits from main result in an automatic snapshot release it works for all commits on main, and it works for manual snapshot releases from branches
• set-version now updates all package.json nested below the current working directory (expect node_modules), so no need for running it each workspace of a monorepo separately.

[changeset-bot]

🦋 Changeset detected

Latest commit: 73c3943

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 26 packages

Name	Type
@latticexyz/cli	Major
@latticexyz/std-client	Major
@latticexyz/dev-tools	Major
@latticexyz/ecs-browser	Major
@latticexyz/block-logs-stream	Major
@latticexyz/common	Major
@latticexyz/config	Major
create-mud	Major
@latticexyz/gas-report	Major
@latticexyz/network	Major
@latticexyz/noise	Major
@latticexyz/phaserx	Major
@latticexyz/protocol-parser	Major
@latticexyz/react	Major
@latticexyz/recs	Major
@latticexyz/schema-type	Major
@latticexyz/services	Major
@latticexyz/solecs	Major
solhint-config-mud	Major
solhint-plugin-mud	Major
@latticexyz/std-contracts	Major
@latticexyz/store-cache	Major
@latticexyz/store-sync	Major
@latticexyz/store	Major
@latticexyz/utils	Major
@latticexyz/world	Major

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[dk1a]

I think you wanna update templates, they still use set-version -v canary

have you seen https://yargs.js.org/docs/#api-reference-conflictsx-y ? not sure it fits this case though

[alvrs]

I think you wanna update templates, they still use set-version -v canary

good catch, updated

have you seen https://yargs.js.org/docs/#api-reference-conflictsx-y ? not sure it fits this case though

We could use it, but would have to add an array of the other 4 elements to each of ["mudVersion", "link", "tag", "commit", "restore"]; so I think in this case the non-yargs solution is easier