Merge Category:Subgroups and Category:Projects to Category:Groups & Projects

Why is this change being made?

This MR merges the categories ~"Category:Subgroups" and ~"Category:Projects" into a single category, Groups & Projects. This is intended to help support the consolidation of categories across grouptenant scale.

There are a few reasons why this would make sense:

• Fewer categories to manage (3 instead of 4), which allows for Organization category: !123157 (merged)
• Projects and groups are consolidated into one namespace object, and a lot of the ongoing work concerns both groups and projects
• Groups and projects are largely interdependent, and talking about them on separate direction pages does not really make sense
  • We have no initiatives planned to specifically improve Projects or features only available at the project level (topics, badges). We would improve Projects in the sense that we align functionality between Projects and Groups.
  • Features that the group owns that relate to Projects, such as membership, sharing, etc. are generally also applicable to Groups
• Groups are a marketing category, but Projects are not
• Groups have a category direction page, but Projects do not

Related issue: #14554 (closed), which creates an Organization category

Approval section

As per the handbook process:

Approvals

• Chief Product Officer: @david
• VP of Product: @mflouton
• Director of Product, Enablement: @joshlambert
• Director of Engineering, Enablement: @cdu1
• Director of Product Design, Enablement: @vkarnes

Informed

• Chief Technology Officer: Joerg
• VP of Development: Christopher
• VP of UX: Christie
• Director of Quality Engineering:
• Engineering Productivity (by @ mentioning @gl-quality/eng-prod)
• Product Marketing Manager relevant to the stage group(s): Saumya
• Senior Manager, Technical Writing
• Engineering Manager for Quality Engineering

Author Checklist

• Provided a concise title for this Merge Request (MR)
• Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
  • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added.
• Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
  • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
  • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
• If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR
  • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.

---