Start using Conventional Commits spec and automate releases

[derberg]

Reason
We want to have a fully automated releases that are triggered by CI and not by a Human (nothing personal humans 😉 ). First we will do it in generator, if it works fine, we will populate it to the rest of the project.

Description

• Introduce https://www.conventionalcommits.org/en/v1.0.0/
• Expect proper PR titles from contributor that follow https://www.conventionalcommits.org/en/v1.0.0/ and have an automated check for it. Use https://github.com/marketplace/actions/conventional-pr-title or https://github.com/marketplace/actions/commitsar-action
• Maintainers must remember to add proper prefix to the commit before squashing and merging the PR
• Set up a GitHub action that will tag repo with proper version that will trigger release. Maybe use https://github.com/marketplace/actions/conventional-changelog-action that will also give us a changelog
• Document it clearly in the contribution guide https://github.com/marketplace/actions/conventional-changelog-action

[derberg]

Some important actions we should look at when working on this one:
https://github.com/actions/create-release
https://github.com/christian-draeger/increment-semantic-version
https://github.com/esamattis/npm-release

and these ones to have whole flow fully automated:
https://github.com/pascalgn/automerge-action
https://github.com/JulienKode/pull-request-name-linter-action - can be configured for conventional commits

[asyncapi-bot]

🎉 This issue has been resolved in version 0.34.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀