Description

With the configuration options update_changelog_on_bump set to True, the command cz bump --get-next crashed, due to the mutual exclusive options --get-next and --changelog/--changelog-to-stdout.

Changing this behavior to still throw a conflict when using both CLI options, but let --get-next take the precedence over update_changelog_on_bump configuration.

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

Expected behavior

Now the configuration options update_changelog_on_bump can be set to whatever you want when using the cz bump --get-next command.

Steps to Test This Pull Request

1. Build a commitizen config with update_changelog_on_bump flag set to true.
2. Add some commits to the target test project.
3. Run cz bump --get-next
4. The command should work and not throw an error.

Additional context