Gather guardian comments together to avoid quota issues

### TL;DR

As we increase guardian entry points in our project we run against quota limits. If it could instead gather this we'd comment less and not have scaling issues.

### Detailed design

```markdown
A more immediate fix is making it so a comment failure doesn't fail guardian.
```

### Alternatives considered

```markdown

```

### Additional information

Failed to report status: failed to report: failed to create pull-request/issue comment with retries: failed to execute retriable function: failed to create pull-request/issue comment: POST https://api.github.com/repos/ORG/REPO/issues/436/comments: 403 You have exceeded a secondary rate limit and have been temporarily blocked from content creation. Please retry your request again later. For more on scraping GitHub and how it may affect your rights, please review our Terms of Service (https://docs.github.com/en/site-policy/github-terms/github-terms-of-service) []

The issue is about reducing GitHub API calls to avoid secondary rate limits when posting comments. Look for where guardian creates issue comments, likely in a client or service handling GitHub interactions. The goal is to batch or deduplicate comments before posting. Check the codebase for 'comment', 'CreateComment', or similar functions. Understanding the guardian's workflow and where it's triggered from CI/CD is needed to implement a gathering mechanism.

Written by the indexing model from the issue text.