Add one off migration files to migrate environments resources

What does this MR do and why?

one-off migration MR for Rename Configure and Release to: Deploy:Environ... (#1278 - closed)

closes #1278 (closed)

Expected impact & dry-runs

current label	label after migration
~"devops::configure"	devopsdeploy
~"devops::release"	devopsdeploy
~"group::configure"	groupenvironments
~"group::release"	groupenvironments
any of the category labels mentioned in here without groupenvironments	the same category label + groupenvironments

See https://gitlab.com/gitlab-org/quality/triage-ops/-/pipelines/814901640 for dry-run jobs

These migrations should run in the following sequence:

• release-to-environments-group
• configure-to-environments-group
• release-configure-to-deploy-stage
• add-environments-group-to-relevant-categories

Action items

• If adding environment variables for reactive processors, update config/triage-web.yaml and .gitlab/ci/triage-web.yml
• (If applicable) Add documentation to the handbook pages for Triage Operations =>
• (If applicable) Identify the affected groups and how to communicate to them:
  • /cc @person_or_group =>
  • Relevant Slack channels =>
  • Engineering week-in-review