Add CI/CD, conventional commit enforcement, and auto release notes

[deanefrati]

No description provided.

[Lutherwaves]

https://github.com/tink3rlabs/example-app/blob/main/.github/workflows/go-test.yml

[Lutherwaves]

Reopening as it was not completed, auto-closed by the PR that contributes to completing this

[Lutherwaves]

Ok. so basically, there are a few main options:

• Pre-commit hook - using tools such as https://commitlint.js.org/guides/getting-started.html, a pre-commit hook can be set up. The drawback is git pre-commit hook can be skipped
• Github Aciton - A Github Aciton that will scan the commits and succeed/fail, using something like https://github.com/webiny/action-conventional-commits

Generally, I lean towards adding the Github Action for the following reasons:

• Easily understand "what went wrong"
• Not blocked on pushing your commits for testing/development (in Draft PRs for example)
• Easier to manage, as pre-commit hooks can definitely be skipped
• Easier to port across repos

The Cons of an Action would be

• It can definitely be skipped if the team member deleted the Action from the .github folder - this can be mitigated by adding a ruleset on the Github Org/Repository to only allow a set of team members to edit the .github folder altogether
• The failure is not left-shifted, and devs would need to wait for the pipeline to pass everytime they push; this may slow down things a tiny bit

[Lutherwaves]

This is also neat https://github.com/siderolabs/conform