feat(bump): add retry_bump_after_failure config option

[EkinDeveci1907]

Description

adds a 'retry_bump_after_failure' config option so 'cz bump' can retry a failed commit without passing '--retry' everytime. This is the same idea as 'retry_after_failure' for 'cz commit'.

this covers action item 2 from #1302. Action item 1 (deprecating 'retry_after_failure' in favour of 'retry_commit_after_failure') is not part of this PR.

Checklist

• I have read the contributing guidelines

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)

Generated-by: Claude following the guidelines

Code Changes

• Add test cases to all the changes you introduce
• Run uv run poe 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

Expected Behavior

with 'retry_bump_after_failure = true' in the config, 'cz bump --changelog' retries the commit once if the first attempt fails (for example when a pre-commit hook reformats the changelog), the same as running 'cz bump --changelog --retry'. the option defaults to 'false', so nothing changes for existing users.

Steps to Test This Pull Request

1. run 'uv run pytest tests/commands/test_bump_command.py -k retry_bump_after_failure'
2. the test turns the option on, makes the first 'git commit' fail and the second one pass, then checks that 'cz bump' tried to commit twice

Additional Context

part of #1302

i ran 'uv run poe lint' and 'uv run poe test' locally and everything passes (1328 passed).

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.28%. Comparing base (b2eb0cb) to head (f334325).
⚠️ Report is 11 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #2100   +/-   ##
=======================================
  Coverage   98.28%   98.28%           
=======================================
  Files          61       61           
  Lines        2862     2865    +3     
=======================================
+ Hits         2813     2816    +3     
  Misses         49       49           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

[Copilot]

Copilot review overview

🟡 Changes recommended

The new option is missing from default settings and user documentation.

Review effort: Balanced
Findings: 1 · 1

Open (2)

• Add retry_bump_after_failure to default settings · New
• Document the retry_bump_after_failure configuration option · New

What changed in this PR

Adds configurable retry behavior for failed cz bump commits.

Changes:

• Adds retry_bump_after_failure.
• Combines the setting with --retry.
• Tests configured retry behavior.

File	Description
commitizen/​defaults.py	Declares the new setting.
commitizen/​commands/​bump.py	Applies configured retry behavior.
tests/​commands/​test_bump_command.py	Tests a failed commit retry.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[bearomorphism]

Approved with documentation suggestions. I didn't validate the new config option on my machine, but the code looks good to me.

cc @woile @Lee-W