Follow-up from "Resolve "Missing MR links on rebased merge train commits (FF merge)""
<!--IssueSummary start-->
<details>
<summary>
Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards.
</summary>
- [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=560171)
</details>
<!--IssueSummary end-->
The following discussion from !195831 should be addressed:
- [ ] @allison.browne started a [discussion](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/195831#note_2672967377):
> follow-up: we should use `Gitlab::ErrorTracking#track_and_raise_for_dev` here. So that we also get the error in sentry and can fix any bugs we see. Since this is still fairly broad error handling. i.e. we would like to at least know if queries time out so we can fix it.
issue