Remove Continuous Integration Scaling Category

The Continuous Integration Scaling Category was introduced when we had no framework for navigating technical initiatives owned by engineering with Product assisting. Now that we have established a working pattern and Blueprint architecture for the scaling efforts alongside dedicated "tiger teams" we can remove the non-marketing category and add the "ci::scaling" features to the Category::Continuous Integration.

Additionally, CI Scaling relies exclusively on technology in SaaS Platforms and features in CI. This means the scope can be naturally managed as a "maintenance" initiative in CI.

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
• Mention the product group Technical Writer to update the documentation metadata
• Share MR in #product, #development, and relevant #s_, #g_, and #f_ slack channels