Add Resiliency to Repo Batch Fetch

[SUSTAPLE117]

more resilient to failed networks during analyze org repo batch fetch

[Copilot]

Pull request overview

This PR aims to make organization repository batch fetching more resilient to transient network/server failures during analysis by adding retry logic in the GitHub and GitLab SCM clients, and by changing how batch-fetch errors are handled during AnalyzeOrg.

Changes:

• Add retry-with-backoff around GitHub GraphQL org repo pagination queries.
• Add retry-with-backoff around GitLab group projects listing calls.
• Change AnalyzeOrg to log and continue on repo batch fetch errors instead of returning immediately.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.

File	Description
providers/gitlab/client.go	Adds retry loop + retryability check for ListGroupProjects calls.
providers/github/client.go	Adds retry loop + retryability check for GitHub GraphQL GetOrgRepos.
analyze/analyze.go	Changes org analysis behavior to skip errored repo batches rather than failing fast.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 4 out of 5 changed files in this pull request and generated 4 comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 4 out of 5 changed files in this pull request and generated 2 comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[fproulx-boostsecurity]

Great