Manage releases using changesets

[trivikr]

Fixes: https://github.com/facebook/jscodeshift/issues/494

The steps maintainers have to take:

• Optional: enable only squash merge on Pull Requests and disable others https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests
  • This step is not required, but will keep the commit history clean.
• Enable https://github.com/apps/changeset-bot which will inform contributors to optionally add a changeset in their PRs.
• Create and store npm publish token in GitHub secret NPM_TOKEN

Changesets Action will create a pull request for publishing new version whenever changesets are available. When the pull request is reviewed and merged, a new GitHub Release will be created and npm version will be published.