fix(bump): write bumped version to stdout even when output config is set

[orhun]

Description

When the output is configured in cliff.toml the --bumped-version overrides the output file.

This is not intuitive... so now we always print to stdout even though [changelog].output is configured.

git cliff --bumped-version --output test keeps working as expected.

Motivation and Context

fixes #1204

How Has This Been Tested?

Locally.

Types of Changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation (no code change)
• Refactor (refactoring production code)
• Other

Checklist:

• My code follows the code style of this project.
• I have updated the documentation accordingly.
• I have formatted the code with rustfmt.
• I checked the lints with clippy.
• I have added tests to cover my changes.
• All new and existing tests passed.

[codecov-commenter]

Codecov Report

❌ Patch coverage is 0% with 3 lines in your changes missing coverage. Please review.
✅ Project coverage is 44.33%. Comparing base (8270084) to head (8e447f0).

Files with missing lines	Patch %	Lines
git-cliff/src/lib.rs	0.00%	3 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1307      +/-   ##
==========================================
+ Coverage   44.32%   44.33%   +0.01%     
==========================================
  Files          22       22              
  Lines        2033     2035       +2     
==========================================
+ Hits          901      902       +1     
- Misses       1132     1133       +1     

Flag	Coverage Δ
unit-tests	44.33% <0.00%> (+0.01%)	⬆️

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.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.