Create new Category:Organization for Group::Tenant Scale

As part of the recent reorganization, Group::Organization was merged with Group::Pods to form Group::Tenant Scale.

This issues serves to create a new Category:Organization.

Why is this change needed?

• Since the team has been renamed to Group::Tenant Scale and the domain of the team has grown larger, there is no natural place such as the group direction page anymore to discuss the Organization.
• The features and settings for an Organization are different from groups and projects.

References

• Organization and Pods team and category naming (gitlab-org/gitlab#391930 - closed)

Process

• https://about.gitlab.com/handbook/product/categories/#changes

Examples

• Rename Sharding team/category to Pods (#13367 - closed)
• Rename Manage:Workspace to Manage:Organization (#14254 - closed)

Approvals

• Chief Product Officer: David
• VP of Product: Mike
• Director of Product, Enablement: Josh
• Director of Engineering, Enablement: Nick
• Director of Product Design, Enablement: Taurie

Informed

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

Things to update

No workflow impact

• Handbook pages | MR
• Update marketing material
  • Slide decks

Potential workflow impact

• stages.yml | MR
• categories.yml | MR
• spec/homepage/category_spec.rb
• Ensure that GitLab Bot auto-labeling can be updated prior to the change
• Update policies/stages/report/quad-planning-issues.yml
• Tag the group Technical Writer in the merge request to ensure documentation metadata is updated after the category change is merged
• Epics
  • Review epics that need the new category added
• Issues
  • Review issues that need the new category added
• Triage Ops - Labels
  • Create new label for category:organization
  • Check whether Triage Ops needs to include the label in workflows
• Update product_group RSpec metadata for E2E tests located in qa/qa/specs/features
• Update Sisense
• Update CODEOWNERS
• Team Page