Remove graphql fields `editor` from workspace type and queries

Deprecation Summary

Under the workspaces domain, The editor field on the graphql type defaults to webide which is inaccurate and could be confused with the Gitlab Web IDE. Since this field does not serve a purpose at the moment. We want to remove it entirely

Documentation

• Deprecation markers have already been added to the schema in Remove references for editor field on workspaces (!167673 - merged)

Product Usage

This removal is inconsequential from a product perspective as there was only ever one option

Breaking Change?

Affected Customers

• GitLab.com
• Self-managed
• Dedicated

Deprecation Milestone

17.7

Planned Removal Milestone

18.0

Links

• Remove deprecated editor field from GraphQL API (#498322)
• Add deprecation announcement on editor field in... (#508160 - closed)

Checklists

Timeline

Rollout Plan

Communication Plan

DRIs:

• Product Manager: @PM

Add links to the relevant merge requests.

• As soon as possible, but no later than the third milestone preceding the major release (for example, given the following release schedule: 17.8, 17.9, 17.10, 17.11, 18.0 – 17.9 is the third milestone preceding the major release):
  • A deprecation announcement entry has been created so the deprecation will appear in release posts and on the general deprecation page.
  • Documentation has been updated to mark the feature as deprecated.
• On the major milestone:
  • The deprecated item has been removed.
  • If the removal of the deprecated item is a breaking change, the merge request is labeled breaking change.
  • Document the migration plan for users, clearly outlining the actions they need to take to mitigate the impact of the breaking change.
    • Add link

Development

Approvals

• Product Manager @PM
• Engineering Manager @EM
• Senior Engineering Manager / Director @senior-eng-leader
• Group / Director of Product Management @senior-product-leader

Mentions (as applicable)

• Product Designer @ProductDesigner
• Tech Writer @TW
• Software Engineering in Test @SET
• Any other stable counterparts based on the product categories:
  • Add Sales/CS counterpart or mention @timtams
  • Add Support counterpart or mention @gitlab-com/support/managers
  • Add Marketing counterpart or mention @cfoster3

Labels

• This issue is labeled deprecation, and with the relevant ~devops::, ~group::, and ~Category: labels.
• This issue is labeled breaking change if the removal of the deprecated item will be a breaking change.

References

• Deprecations, removals, and breaking changes
• Deprecation guidelines
• Deprecations and removals doc styleguide
• REST API Deprecations and REST API breaking changes.
• GraphQL Deprecations and GraphQL API breaking changes.
• GitLab release and maintenance policy
• Videos 📺
  • How to deprecate and remove features in GitLab releases
  • Review of GitLab deprecations and removals policy & Runner team deprecations and removals process