TW group change: Deploy / Environments moves to Verify / Runner Core

Use this template to manage changes when there is a new stage/group, a deprecated stage/group, or when a group moves to a different stage.

Stage/group change: devopsdeploy / groupenvironments => devopsverify / Runner Core
Stable counterpart technical writer(s) affected: @rsarangadharan
Technical writing manager affected: @michael.belton
Group change expected to be complete by: 18.4

Tasks for assigned technical writer

In the www-gitlab-com repository:
- Check that an update for data/stages.yml is in progress, and link the MR to this issue. A group or stage change is usually initiated by a Product Manager or Engineering Manager, who is responsible for following the process for Changes. It the PM or EM's responsibility to raise the MR to update stages.yml.
- Once the stages.yml MR is merged, check that the changes are reflected in Assignments to DevOps Stages and Groups. The assignments table automatically pulls in the data from stages.yml. There should be no additional action required.
In the gitlab repository, update as needed (in the following order, but can be done in the same MR):
1. The metadata in all related markdown files.
2. Group assignments in lib/tasks/gitlab/tw/codeowners.rake.
3. .gitlab/CODEOWNERS by running the tw:codeowners Rake task to ensure no pages are missed.
In the Technical Writing project, update the Milestone Planning template.

Update the TW Tableau dashboard. For instructions, refer to the internal handbook.
If this transition impacts a group with a stage lead, update the list of TWs for the stage in the stage lead issue script and in the current milestone planning issue.
Update google sheets used for team rebalancing planning.