feat: add commitizen cli and commit standards

[kenibrewer]

Description

Commitizen pre-installed cli will aid in the generation of commit messages can be used for automatic changelog generation.

Address #333

What is the nature of your change?

• Enhancement (adds functionality).
• This change requires a documentation update.

Checklist

Please ensure that all boxes are checked before indicating that a pull request is ready for review.

• I have read the CONTRIBUTING.md guidelines.
• My code follows the style guidelines of this project.
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• I have made corresponding changes to the documentation.
• My changes generate no new warnings.
• I have deleted all non-relevant text in this pull request template.

[codecov-commenter]

Codecov Report

Merging #340 (cd6ef6b) into main (7b97db7) will not change coverage.
Report is 2 commits behind head on main.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #340   +/-   ##
=======================================
  Coverage   95.40%   95.40%           
=======================================
  Files          56       56           
  Lines        3135     3135           
=======================================
  Hits         2991     2991           
  Misses        144      144           

Flag	Coverage Δ
unittests	95.40% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[d33bs]

Nice work! These were thoughtful additions and appreciate the additional context in the PR description. I left a few comments which I hope to get your feedback on before an approval. Mostly here I wonder / worry about what happens with squashes and those who might be new to the procedures (and also might be developing locally instead of in the devcontainer).

[kenibrewer]

@d33bs I made the following changes since your last review:

• Went back to installing commitizen via poetry dev group. It turns out the previously used dev container feature is from an identically named (but separate) commitzen project from the js community. I took a closer look at the version restrictions I was worried about, but the relevant packages only moved back a few months from the latest version. Commitizen is also under active development so I'm less worried about the impacts.
• Removed the commitizen precommit hook for further discussion and possible integration post 1.0.
• Modifed the language about formatting to be dev environment agnostic.

[d33bs]

Thanks for the replies and follow up comments - LGTM.