Rename Category:Pods to Category:Cell

Why is this change being made?

As part of the recent reorganization, Group::Organization was merged with Group::Pods. The term Pods conflicts with Kubernetes Pods and is not descriptive enough of the common goal of the team, which is to find a horizontal scaling solution. Thoughts on the exact reasoning for selecting Cells as a team name are summarised here and here.

TL;DR:

• Group name becomes Cells (#g_cells) which is coherent with current group name of Pods: plural, we are meant to deliver many Cells, each Cell having many Organizations
• Group name is after a key feature that we are meant to deliver
• Categories that the team owns are then Category:Organization and Category:Cell

#14553 (closed)

Approvals

• Chief Product Officer: David
• VP of Product: Mike
• Director of Product, Enablement: Josh
• Director of Engineering, Enablement: Chun
• Sr Manager of Product Design, Enablement: Taurie
• Director of Product Design @vkarnes

The following people need to be on the merge request so they stay informed:

• Vice President of Development @clefelhocz1
• Vice President of Quality @meks
• Vice President of User Experience @clenneville
• The Product Marketing Manager relevant to the stage group(s)
• Director of Technical Writing @susantacker

After Approvals and Merge

• Create an issue in the triage-ops project to update GitLab Bot automation:
  • for Category change
  • for Stage or Group change
• Mention the product group Technical Writer to update the documentation metadata
• Share MR in #product, #development, and relevant #s_, #g_, and #f_ slack channels

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, and the content is SAFE
• 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
  • The when to get approval handbook section explains the workflow in more detail
• 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.

---