Issue Summary:
The "Ignore Committer Strategy" plugin does not skip builds as expected for commits made by excluded users when using Multibranch Pipeline with Bitbucket Cloud SCM. Despite the plugin configuration specifying an email to exclude, builds are still triggered by webhooks, and errors are logged in Multibranch Pipeline Events.

 
Steps to Reproduce:
Set up a Multibranch Pipeline connected to a Bitbucket Cloud repository.
Enable "Ignore Committer Strategy" under "Build Strategies" in Branch Source configuration.
Add an email address to exclude a specific committer (e.g., jenkins@example.com).
Push changes to a Bitbucket PR using the excluded committer.
Observe that builds are still triggered.
 
Expected Behavior:
Pipeline should skip builds triggered by changes from the excluded committer.
 
Actual Behavior:
Builds start despite the plugin configuration. In Multibranch Pipeline Events, an error line appears in the logs.
 
Log Snippet from Events:

[Fri Nov 29 21:26:16 UTC 2024] Received com.cloudbees.jenkins.plugins.bitbucket.hooks.PullRequestHookProcessor$HeadEvent UPDATED event from 104.192.140.243 ⇒ https://myjenkins.com:8080/bitbucket-scmsource-hook/notify/ with timestamp Fri Nov 29 21:26:11 UTC 2024
Connecting to https://bitbucket.org using ******
Looking up myworkspace/myrepo for pull requests
Initialized PR: https://bitbucket.org/myworkspace/myrepo/pull-requests/3
Checking PR-3 from myworkspace/myrepo and branch test-ics
      ‘ci/Jenkinsfile’ found
    Met criteria
Changes detected: PR-3 (61e00059f64c+6e6181e8793c → 27e1b5cfa306+6e6181e8793c)
ERROR: Exception: org.eclipse.jgit.errors.InvalidObjectIdException: Invalid id: 27e1b5cfa306
Scheduled build for branch: PR-3
  1 pull requests were processed (query completed) 

 
Additional Information:
This issue is specific to Bitbucket. Testing the same setup with GitHub works as expected, and builds are skipped correctly.
Bitbucket webhook is correctly configured and triggers builds as expected in other scenarios.