….commitizen.customize

Description

Adds ability to override settings using [tool.commitizen.customize] in the cz_conventional_commits

Checklist

• I have read the contributing guidelines

Code Changes

• Add test cases to all the changes you introduce
• Run poetry all locally to ensure this change passes linter check and tests
• Manually test the changes:
  • Verify the feature/bug fix works as expected in real-world scenarios
  • Test edge cases and error conditions
  • Ensure backward compatibility is maintained
  • Document any manual testing steps performed
• Update the documentation for the changes

Documentation Changes

• Run poetry doc locally to ensure the documentation pages renders correctly
• Check and fix any broken links (internal or external) in the documentation

Expected Behavior

You use conventional_commits commitizen, and using [tool.commitizen.customize] config section you override selected settings

Steps to Test This Pull Request

Add this to pyproject.tomp in existing project using conventional_commits and update_changelog_on_bump = true:

[tool.commitizen.customize]
change_type_map = {"feat" = "✨ Feat", "fix" = "🐛 Bug Fix", "refactor" = "♻️  Refactor", "perf" = "⚡️ Perf"}

do cz bump --dry-run and observe that changelog headers have gitmoji.
Test that other behavior is identical to unpatched version
test that
bump_map = {"^.+!$" = "MAJOR", "^feat" = "MAJOR", "^fix" = "MINOR", "^refactor" = "MINOR", "^perf" = "MINOR"} bumps MINOR not PATCH part on fix commit, test that other things are unchanged.
Test other settings.

Additional Context

This is starting shot at #1385
To test this I copied tests for cz_customize, removed name=... from all configs there and removed the tests that don't make
sense, for example exception for missing customize section.