Github Check Runs: Support server-side filtering for GitHub Check Runs via check_name

:clipboard: **Description**

**Problem**: The nameFilter parameter in the GithubCheckRuns service does client-side filtering on the first page of results. For repositories with many check runs, the target check run may be on page 2+ and is never fetched. The badge returns "no check runs" even though the check exists.

**Fix**: GitHub's [List check runs for a git reference API](https://docs.github.com/en/rest/checks/runs#list-check-runs-for-a-git-reference) supports a check_name query parameter for server-side filtering. Passing nameFilter as check_name would make GitHub return only matching check runs, eliminating the pagination issue entirely.

I'd be happy to submit a PR for this:)

Start at the GithubCheckRuns service and review how its nameFilter is applied when calling GitHub's List check runs for a git reference API. Confirm the API's check_name query parameter behavior, then verify that a matching check run is found even when it would otherwise be beyond the first results page.

Written by the indexing model from the issue text.