GraphQL for Sentry error details

What does this MR do?

This adds a GraphQL field for reading details error details for a Sentry Error. This is the GraphQL equivalent for the REST endpoint GET /*namespace_id/:project_id/error_tracking/:issue_id/details, added here: !19137 (merged).

This is the first GraphQL endpoint for the devopsmonitor stage, and so it will hopefully serve an an example to build upon.

Next steps to add are to round out the Sentry Error endpoints.

Issues to do so:

• Add a GraphQL query for Error Tracking - list projects
• Add a GraphQL query for Error Tracking - Stack trace
• Add a GraphQL query for Error Tracking - List Errors

A sentry error can be queried with a GraphQL query like the following:

{
  project(fullPath: "root/monitor-sandbox") {
    sentryDetailedError(id: "gid://gitlab/Gitlab::ErrorTracking::DetailedError/1291455262") {
      id
      sentryId
      title
      type
      userCount
      count
      firstSeen
      lastSeen
      message
      culprit
      externalUrl
      projectId
      projectName
      projectSlug
      shortId
      status
      frequency
      firstReleaseLastCommit
      lastReleaseLastCommit
      firstReleaseShortVersion
      lastReleaseShortVersion
    }
  }
}

We use Global IDs for the Project and Sentry Error, which explains the long gid:// param for issueId.

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

Closes #34943 (closed)