chore(Commitizen): Don't bump major version

Normally, Commitizen, in compliance with semantic versioning, bumps the
project's major version on breaking changes. At major version 0, any
release can have breaking changes, and bumping the major version to 1
signifies the stability of the public API. We are currently at major
version 0, so configure Commitizen not to bump the major version on
breaking changes.

Author: Kurt-von-Laven

pyproject.toml

@@ -6,6 +6,7 @@ build-backend = "poetry.core.masonry.api"
   [tool.commitizen]
   version = "0.7.2"
   version_files = ["pyproject.toml:version"]
+  major_version_zero = true
 
   [tool.poetry]
   name = "GitHub Starter Workflows"