Add metadata about the GitLab server to GraphQL

What does this MR do?

Implements a "metadata" graphql resource that duplicates the REST /version endpoint, and transforms the latter into a graphql client for the former

What are the relevant issue numbers?

Does this MR meet the acceptance criteria?

• Changelog entry added, if necessary
• Documentation created/updated via this MR
• Documentation reviewed by technical writer or follow-up review issue created
• Tests added for this feature/bug
• Tested in all supported browsers
• Conforms to the code review guidelines
• Conforms to the merge request performance guidelines
• Conforms to the style guides
• Conforms to the database guides
• Link to e2e tests MR added if this MR has Requires e2e tests label. See the Test Planning Process.
• Security reports checked/validated by reviewer

Related to #56809 (closed)

added GraphQL backstage [DEPRECATED] labels

mentioned in issue #56809 (closed)

changed the description

added 1 commit

• 8d02feb3 - Reimplement the REST /version API as a GraphQL query

Compare with previous version

added 1 commit

• 6543a68e - Add metadata about the GitLab server to GraphQL

Compare with previous version

assigned to @reprazent

@reprazent do you mind looking at this and adding your thoughts sometime? I guess I'm interested in the code itself, and also the idea of making this the recommended thing to do when creating overlap with some part of the REST API in graphql.

If you can pass it to @DouweM after you're done for further comment, that'd be great. I don't think we should merge it right now, so it's WIPped.

Is graphql still behind a feature flag? That would be one reason why we couldn't merge something like this in %11.8

Is graphql still behind a feature flag? That would be one reason why we couldn't merge something like this in %11.8

It is, but it's enabled by default. I don't know if that's enough to be able to merge it. But we could have a dependent feature flag for these migrations?

I guess I'm interested in the code itself, and also the idea of making this the recommended thing to do when creating overlap with some part of the REST API in graphql.

I love the idea of recommending this, but I guess we'd need to add some helpers to facilitate migrating before we do.

@DouweM What are your thoughts?

assigned to @DouweM

added 51 commits

• 6543a68e...47e6675c - 50 commits from branch gitlab-org:master
• 415f5106 - Add metadata about the GitLab server to GraphQL

Compare with previous version