For Suspect Commits, ignore commits from .git-blame-ignore-revs

### Environment

SaaS (https://sentry.io/)

### Steps to Reproduce

1. Write some code that will trigger a Sentry error
2. Add your commit to .git-blame-ignore-revs
3. Push the code live and trigger the bug

### Expected Result

Sentry does not suggest that commit in the Suspect Commit

### Actual Result

Sentry shows that commit as the Suspect Commit

### Product Area

Issues

### Link

_No response_

### DSN

_No response_

### Version

_No response_

The issue names no files, tests, or entry points. Start by locating the suspect-commit selection path and how repository blame exclusions are handled; reproduce the listed steps, then verify commits present in .git-blame-ignore-revs are no longer suggested as suspect commits.

Written by the indexing model from the issue text.