[Feature flag] Rollout of `ci_pipeline_editor_page`

What

The Pipeline Editor is becoming the new home of the grouppipeline authoring team. It will house our text and visual pipeline editor, along with a preview of the pipelines they'll have as users update them.

Remove the :ci_pipeline_editor_page feature flag.

Current Implementation State

You may view the current state of implementation at workflowstaging:

https://staging.gitlab.com/gitlab-org/gitlab/-/ci/editor

This page may take a few iterations before becoming public, and we will want approval of our Product and UX team members.

Owners

• Team: grouppipeline authoring
• Most appropriate slack channel to reach out to: #g_pipeline-authoring
• Best individual to reach out to: @mrincon

Expectations

A new pipeline editor is added with a simple UX as a first iteration.

What are we expecting to happen?

What might happen if this goes wrong?

What can we monitor to detect problems with this?

Beta groups/projects

If applicable, any groups/projects that are happy to have this feature turned on early. Some organizations may wish to test big changes they are interested in with a small subset of users ahead of time for example.

• gitlab-org/gitlab project
• gitlab-org/gitlab-com groups
• ...

Roll Out Steps

• Enable on staging (/chatops run feature set feature_name true --staging)
  • Enabled on globally on staging: https://staging.gitlab.com/gitlab-org/gitlab/-/ci/editor
• Test on staging
• Ensure that documentation has been updated
  • Issue: #297367 (closed)
• Enable on GitLab.com for individual groups/projects listed above and verify behaviour (/chatops run feature set --project=gitlab-org/gitlab feature_name true)
  • Enabled on samdbeckham/test: https://gitlab.com/samdbeckham/test/-/ci/editor
• Coordinate a time to enable the flag with #production and #g_delivery on slack.
• Announce on the issue an estimated time this will be enabled on GitLab.com
• Enable on GitLab.com by running chatops command in #production (/chatops run feature set feature_name true)
• Cross post chatops Slack command to #support_gitlab-com (more guidance when this is necessary in the dev docs) and in your team channel
• Announce on the issue that the flag has been enabled
• Remove feature flag and add changelog entry
• After the flag removal is deployed, clean up the feature flag by running chatops command in #production channel