Setup a git commit message convention

The commit message should be structured as follows:

<type>(<optional scope>): <subject>
<optional body>
<optional footer>

Types

feat: Commits, that adds a new feature
fix: Commits, that fixes a bug
refactor: Commits, that rewrite/restructure your code, however does not change any behaviour
perf: Commits are special special refactor commits, that improve performance
style: Commits, that do not affect the meaning (white-space, formatting, missing semi-colons, etc)
tests: Commits, that add missing tests or correcting existing tests
docs: Commits, that affect documentation only
build: Commits, that affect build components like build tool, ci pipeline, dependencies, project version, ...
Ops: Commits, that affect operational components like infrastructure, deployment, backup, recovery, ...
chore: Miscellaneous commits e.g. modifying .gitignore