Cherry-picked commit not detected properly as part of the release

  1. We had a last-minute revert before release day: gitlab-org/gitlab!95682 (merged)
  2. Something went wrong? (I think?) and we needed to cherry-pick the merge commit: https://gitlab.com/gitlab-org/security/gitlab/-/commit/3cba3e837e73a8f0fd6a2e770ecfb824e74af2f0. Therefore the hash of the commit was changed.
  3. /chatops run release check https://gitlab.com/gitlab-org/gitlab/-/merge_requests/95682 15.3 responds with gitlab-org/gitlab!95682 has not been included in the stable branch. The MR will not be released in 15.3.

Maybe we could improve the retrieval logic to find cherry-picked commits as well.

Seems like we are using https://docs.gitlab.com/ee/api/commits.html#get-references-a-commit-is-pushed-to to find the references a commit is pushed to. Maybe it makes sense parsing the last X commits as well, if the above method fails.