Update order of description and status in graphql docs

What does this MR do and why?

For GraphQL endpoints that have a details/status in the reference doc, the details should come first, then the description, but right now it's backwards. For example: https://docs.gitlab.com/api/graphql/reference/#queryabusereport

Our style requires the details to be after the header, otherwise it doesn't render properly. See more examples at https://docs.gitlab.com/development/documentation/styleguide/availability_details/

This MR flips things around so the details section comes first.

References

• Resolves #554436 (closed)

Screenshots or screen recordings

• Before: https://docs.gitlab.com/api/graphql/reference/#queryabusereport
• After: https://docs.gitlab.com/upstream-review-mr-ee-197782/api/graphql/reference/#queryabusereport

Before	After

How to set up and validate locally

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.