Rename Create::Editor to Create::IDE

More details can be found in Rename Create:Editor to reflect new focus (Product#5491 - closed)

The Create::Editor group's scope of work has significantly changed and the group name no longer accurately reflects the categories within.

This MR renames the group to Create::IDE.

Why "IDE"?

• The group no longer oversees a the broad "editing" experience, or even "code editing" experience, within GitLab. groupsource code and groupknowledge are both responsible for significant aspects of the code and content editing components. Keeping the name Editor or using a broad derivative would introduce confusion.
• A significant amount of our focus is on Remote Development, however the Web IDE and GitLab Workflow extension are not really "remote" development. We also want to avoid having to re-name the existing category Remote Development because of its clear purpose and place in the market.
• IDE describes both the features of the group and the places in which we expect users to interact with our features.

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) - @justinfarris
• The Engineering Director relevant to the affected Section(s) - @dsatcher
• 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) @heather
• 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
  • If label migration is required, please follow the self-serve instructions to get started on a one-off label migration MR.
• Mention the product group Technical Writer to update the documentation metadata
• Share MR in #product, #development, and relevant #s_, #g_, and #f_ slack channels