fix(bitbucket): match PR and release metadata correctly

[mcwarman]

Description

Fixes Bitbucket pull request matching to release metadata:

• update BitbucketPullRequest struct to use merge_commit
• update metadata matching to support short sha format
• add tests for Bitbucket remote

Motivation and Context

When testing the Bitbucket integration the pull request matching does not work. Commits are not being matched to pull requests looking into the API response it looks to be for two reasons

Fixes #905

How Has This Been Tested?

git clone git@bitbucket.org:mcwarman-playground/playground.git
cd playground
~/code/src/github.com/orhun/git-cliff/target/debug/git-cliff --current --context --bitbucket-repo "mcwarman-playground/playground" | jq .

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.

[welcome]

Thanks for opening this pull request! Please check out our contributing guidelines! ⛰️

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 40.85%. Comparing base (508a97e) to head (cb169a3).
Report is 96 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #907      +/-   ##
==========================================
+ Coverage   40.12%   40.85%   +0.73%     
==========================================
  Files          21       21              
  Lines        1675     1677       +2     
==========================================
+ Hits          672      685      +13     
+ Misses       1003      992      -11     

Flag	Coverage Δ
unit-tests	40.85% <100.00%> (+0.73%)	⬆️

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.

[orhun]

LGTM!

One thing that we can do is to assert this behavior is updating the test-bitbucket-integration fixture to use your playground repository instead of my testing repository (git-cliff-readme-example)

Here you can find some instructions about how the test fixtures work. It should be pretty straightforward though.

I think I initially missed this bug since the fixture does not contain anything about handling the PRs :)

[mcwarman]

I've updated the fixtures, I decided to fork your repo and add a PR to it.

[orhun]

LGTM, thanks!

[welcome]

Congrats on merging your first pull request! ⛰️