feat(bump): add commit filter pattern - #2078

Description

This change adds support for filtering commits before Commitizen evaluates them for version bumps by introducing a new bump_commit_filter_pattern setting.

The new setting defaults to .*, so existing projects keep the current behavior. When configured, cz bump and cz version --next USE_GIT_COMMITS only consider commits whose full message matches the filter pattern before applying the existing bump rules. This is particularly useful for monorepos where only a subset of commits should affect a package's version.

The pull request also updates the related documentation and adds regression tests covering the new filtering behavior and fallback paths.

Checklist

• I have read the contributing guidelines

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

• Yes (GitHub Copilot CLI)

Generated-by: GitHub Copilot CLI 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

Documentation Changes

• Run uv run poe doc locally to ensure the documentation pages renders correctly
• Check and fix any broken links (internal or external) — There were no broken links.

Expected Behavior

Projects can opt into filtering commits used for bump calculation without changing the default behavior for existing users. With bump_commit_filter_pattern configured, unrelated commits are ignored before bump_pattern is applied, so cz bump and cz version --next USE_GIT_COMMITS derive the next version only from relevant commits.

Steps to Test This Pull Request

1. Configure Commitizen with bump_commit_filter_pattern for a subset of commit messages, for example ^fix\(library-b\):.
2. Create a baseline tag and add commits that include both matching and non-matching messages.
3. Run cz bump --dry-run or cz bump --get-next and confirm that only matching commits affect the calculated increment.
4. Run cz version --project --next USE_GIT_COMMITS and confirm it reports the version derived from the filtered commit set.
5. Remove the setting or leave it at the default and confirm the previous behavior is preserved.

Additional Context

Related discussion: #2075

Manual testing and validation performed during development included targeted pytest coverage for:

• commit filtering in bump calculation
• USE_GIT_COMMITS next-version calculation with filters
• fallback behavior when no explicit filter is configured
• configuration and documentation updates for the new setting