test: add test for 'additional' types in conventional commits

[woile]

Description

This tests should pass, relates to:
#673

Checklist

• Add test cases to all the changes you introduce
• Run ./scripts/format and ./scripts/test locally to ensure this change passes linter check and test
• Test the changes on the local machine manually
• Update the documentation for the changes

[codecov]

Codecov Report

Patch coverage: 100.00% and project coverage change: -0.05 ⚠️

Comparison is base (6096b68) 97.38% compared to head (376427c) 97.34%.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #728      +/-   ##
==========================================
- Coverage   97.38%   97.34%   -0.05%     
==========================================
  Files          42       42              
  Lines        2029     2034       +5     
==========================================
+ Hits         1976     1980       +4     
- Misses         53       54       +1     

Flag	Coverage Δ
unittests	97.34% <100.00%> (-0.05%)	⬇️

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

Impacted Files	Coverage Δ
commitizen/__version__.py	100.00% <100.00%> (ø)
commitizen/bump.py	100.00% <100.00%> (ø)
commitizen/defaults.py	100.00% <100.00%> (ø)

... and 2 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[woile]

What do you think of this @Lee-W @jenstroeger ?

It won't show the title ### BREAKING CHANGE. But it's the best I could do with the new regex, I cannot repeat the breaking group in here:

https://github.com/commitizen-tools/commitizen/pull/728/files#diff-c951de16d627d82e01eb3ce8d7c4f0b28973ffe147520620762e7140ede2dd80R115

[woile]

@Lee-W I'm gonna merge this and #728 tomorrow, let me know of any comment, it's mostly fixes