Limit amount of data sent with Sentry list

What does this MR do?

Part of #14926 (closed)

Overview

Returns an error response with appropriate status codes in the Projects::ErrorTrackingController and does not store sentry issue data in redis if the data returned from the integrated sentry list issues endpoint is over 1 MB.

Technical Details

This merge request raises a Sentry::Client::ResponseInvalidSizeError if the response is too large when requesting to get a list of sentry issues.

ErrorTracking::ProjectErrorTrackingSetting calls the sentry client to get issues via reactive caching and the raised error is then rescued and converted to a hash.

Finally, the ErrorTracking::ListIssuesService calls the list issues method from ProjectErrorTrackingSetting and the error is rendered by the Projects::ErrorTrackingController.

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

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