feat(bump_rule): add BumpRule, VersionIncrement, Prerelease Enum

[bearomorphism]

Related issue: #129
Original PR: #1431

Description

Please see bump_rule.py, bump.py, cz/base.py, version_scheme.py and commands/bump.py (~350 lines).
The rest 1000+ lines are just tests and renaming.

• Rewrote the bump pattern matching mechanism to make the algorithm more strict and maintainable.
• Maintained backward compatibility with CustomBumpRule.
• Simplified code.
• Added a new Enum class SemVerIncrement and replace MAJOR, MINOR, PATCH with the Enum.
• Now Prerelease is Enum.
• Simplify find_increment logic in SemVerIncrement.get_highest_by_messages.
  • find_increment was the combination of 2 features: "finding the highest semantic version increment" and "parsing the semantic version increment from each git commit message".

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

Expected Behavior

Steps to Test This Pull Request

Additional Context

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.71%. Comparing base (120d514) to head (9644e1a).
⚠️ Report is 842 commits behind head on master.

Additional details and impacted files

@@ Coverage Diff @@## master #1518 +/- ## ========================================== + Coverage 97.33% 98.71% +1.37%  ========================================== Files 42 61 +19 Lines 2104 2722 +618 ========================================== + Hits 2048 2687 +639 + Misses 56 35 -21 

Flag	Coverage Δ
unittests	98.71% <100.00%> (+1.37%)	⬆️

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

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[Lee-W]

This is definitely a great pull request that cleans up a lot of legacy code. However, we need to be cautious about maintaining backward compatibility. We can likely add some of the logic incrementally while keeping compatibility for a few minor versions. After that, we can bump the major version and remove the compatibility handling code.

[Lee-W]

this might be a breaking change for other non-standard czs

[Lee-W]

We'll need a way to keep backward compatibility or move it to 5.0.0 instead (but that would be a pity since the PR looks os good)

[bearomorphism]

Could you provide more details about why this might be a breaking change for non-standard cz s? I am not familiar with non-standard cz. Thanks

[bearomorphism]

Can we do squash rebase on this PR when it is ready for merge?

[Lee-W]

Can we do squash rebase on this PR when it is ready for merge?

yep, I can do that

[bearomorphism]

What are the next steps for this PR? If there are backward compatibility issues, I can adjust it so that this PR can be checked in. Thanks

[bearomorphism]

Core feature change

[bearomorphism]

We can get back to this PR after #1598

[bearomorphism]

@Lee-W It would be great if we can complete this big PR. I can fix those backward-compatibility issues, but I need more details so I can address the issues.

[bearomorphism]

(I've resolved merge conflicts for several times for this PR)

[Lee-W]

This would fall into 4.11.0. Let's foucs on merging the non-features PRs first and then get back to this one.