Merge Kubernetes Management, Advanced Deployments into the Deployment Management category

Related to: The Configure & Release stages become the Deplo... (Product#5530 - closed)

This MR merges the Kubernetes Management and Advanced Deployments categories with the Deployment Management category. The new category will be responsible for every deployment related functionality of GitLab, including cloud-native and legacy infrastructures, deployments to ephemeral, non-production and production environments, advanced release strategies.

We will move the agent for Kubernetes and Kubernetes compatibility under this category too. While the agent is the generic backbone of every GitLab - Kubernetes communication, the team focusing on it maintains its deployment and environments related aspects only. Keeping a separate group (Kubernetes Management) for the framework aspect might mislead our users thinking that we aim more integrations in that domain.

Previously, an alternative name was considered, "Cloud-native deployments`. We decided to go with the more generic "Deployment management" to have a place for non-cloud-native deployments. This will not change our focus from being Kubernetes-first.

Merging the direction pages will happen in a follow-up MR.

Approvals

Merge requests with changes to stages and groups and significant changes to categories need to be created, approved, and/or merged by each of the below:

• Chief Product Officer @david
• The Product Director relevant to the affected Section(s)
• The Engineering Director relevant to the affected Section(s)
• 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
  • If label migration is required, please follow the self-serve instructions to get started on a one-off label migration MR.
• Mention the product group Technical Writer to update the documentation metadata
• Share MR in #product, #development, and relevant #s_, #g_, and #f_ slack channels