Add Group.mergeRequests field

What does this MR do?

This adds a missing piece of GraphQL query functionality: ability to fetch all MRs in an arbitrary parent namespace.

I required this to update my personal CLI tooling to list MRs by group.

Addresses: #217475 (closed)

Queries

This allows the following queries:

All MRs:

query($path: ID!) {
  group(fullPath: $path) {
    mergeRequests { nodes { id } }
  }
}

MRs by author:

query($path: ID!, $user: String) {
  group(fullPath: $path) {
    mergeRequests(authorUsername: $user) { nodes { id author{ username } } }
  }
}

MRs by assignee:

query($path: ID!, $user: String) {
  group(fullPath: $path) {
    mergeRequests(assigneeUsername: $user) { nodes { id } }
  }
}

Traverse subgroups (defaults to off):

query($path: ID!) {
  group(fullPath: $path) {
    mergeRequests(includeSubgroups: true) { nodes { id } }
  }
}

And all other filters and combinations of filters included on merge requests resolvers.

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