feat(context): add release commit range

[jdrst]

Description

Adds the used commit_range for each release.
commit_range includes the full length commit ids (commit_range.from and commit_range.to)
Also added related docs (and documentation for the sort_commits default)

Motivation and Context

See #1041

How Has This Been Tested?

Via integration_test and three new fixtures.

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.

random sideinfo:
repo::test::propagate_error_if_no_repo_found fails under windows.
clippy also reports errors under windows.

[codecov-commenter]

Codecov Report

❌ Patch coverage is 23.07692% with 10 lines in your changes missing coverage. Please review.
✅ Project coverage is 40.04%. Comparing base (451a694) to head (9030e40).
⚠️ Report is 177 commits behind head on main.

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

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1138      +/-   ##
==========================================
- Coverage   40.16%   40.04%   -0.12%     
==========================================
  Files          21       21              
  Lines        1900     1911      +11     
==========================================
+ Hits          763      765       +2     
- Misses       1137     1146       +9     

Flag	Coverage Δ
unit-tests	40.04% <23.08%> (-0.12%)	⬇️

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.

[jdrst]

ah interesting. i just updated my toolchain under windows so the clippy errors (and the linting error here) are probably explained by that.

[orhun]

Looking pretty good, thanks for reopening the PR!

Only got one question

[orhun]

Awesome, thanks for bearing with me!

[welcome]

Congrats on merging your first pull request! ⛰️

[jdrst]

Awesome, thanks for bearing with me!

Same to you :D