Automated Releases

[rperryng]

Currently releases have to be manually cut by a maintainer.

We should:

1. Add some automation so that the version/changelog is bumped automatically, based on conventional commits
2. conventional commits (or some other related mechanism) is enforced
3. releases are published to rubygems by CI

The official JS graphql-hive uses the changesets library which doesn't support ruby (and would require using yarn).

Some other tools that may fit the job:

• Google's "Release Please" generates PRs based on conventional commits on main, the PR will include the version bump / changelog
  • I don't think this tool would support bumping the secondary Gemfile.lock in the k6 directory, but a CI workflow that runs on release PRs can probably address this.