automated release process

[gasparnagy]

🤔 What's changed?

The GitHub workflows are modified to allow automated releases for people having permission for it.

The protection is performed though the environment production_environment that requires manual approval and can be used only from main branch. This environment contains the nuget.org publish key as well.

In addition to publishing the packages to nuget.org, it also creates a GitHub release as well for each production (non-preview) release that is deployed.

Also the PR performs an automatic "version bump" and adds a new section to the CHANGELOG.md after publishing a production release. This is committed / pushed back to the repository.

The Git push is secured with a special deployment key that is registered to the project at https://github.com/reqnroll/Reqnroll/settings/keys. The private key (that is required to initiate the push) is stored as a secret in the environment production_environment.

⚡️ What's your motivation?

• reduce release errors
• reduce "bus factor"

🏷️ What kind of change is this?

• 🏦 Refactoring/debt/DX (improvement to code design, tooling, etc. without changing behaviour)

♻️ Anything particular you want feedback on?

📋 Checklist:

• I've changed the behaviour of the code
• My change requires a change to the documentation.
  • I have updated the documentation accordingly.

---

This text was originally taken from the template of the Cucumber project, then edited by hand. You can modify the template here.

[ajeckmans]

I read through the pipeline and although it is a bit long with all of the scripts inside it is doable.
The documentation part makes sense, so it looks good to me :)