Handle errors with repos api

What does this MR do?

This MR catches an error while attempting to link a Sentry issue to a GitLab issue. The error is only expected to happen in very rare circumstances. Unfortunately, those rare circumstances are with sentry.gitlab.net.

Context

When attempting to create a GitLab issue from a Sentry Error through the GitLab UI, the reciprocal link in Sentry should be created where possible. This mostly works! But there's a bug specifically with sentry.gitlab.net that we should handle.

Basically, something seems to be amiss with the repo data/structure in sentry.gitlab.net. As we aren't utilizing these features at this time (and generally won't be able to unless Sentry makes some major changes to the integration architecture), I'm inclined not to worry about it for the time being. Navigating to https://sentry.gitlab.net/settings/gitlab/repos/ actually reproduces the same error (Notably the call to https://sentry.gitlab.net/api/0/organizations/gitlab/repos/?status= in the background). So this is not a problem we would expect to see often.

Related issue: #37307 (closed)

Screenshots

Does this MR meet the acceptance criteria?

Conformity

• [-] Changelog entry
• [-] Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• [-] Database guides
• [-] Separation of EE specific content

Availability and Testing

• [-] Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• [-] Tested in all supported browsers
• [-] Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• [-] Label as security and @ mention @gitlab-com/gl-security/appsec
• [-] The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• [-] Security reports checked/validated by a reviewer from the AppSec team