Introduce Stage Deploy and Group Environments

As we merge the Release and Configure stages, we had to come up with a new name for the stage and the group within it. This MR implements the decision of using Stage Deploy and Group Environments.

This is the first step in the administrative process of merging the two stages. Follow-up steps will remove and merge product categories, update the team page, etc.

The important changes are in

• stages.yml
• categories.yml

Everything else was changed only to make the pipelines pass and the consequences of the changes in these two files.

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) @mflouton
• The Engineering Director relevant to the affected Section(s) @sgoldstein
• 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) @anair5
• 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