Description of problem:

Configuring the CheCluster config such that `.spec.containerRegistry` points to a mirror registry does not affect the default editor definitions, causing those images to still pull from the Red Hat catalog (upstream).

These editor definitions should be found within the `editors-definitions` ConfigMap in the Dev Spaces namespace, but these are practically immutable as the controller will set them back to the default. As such, they cannot be configured to use the downstream images.

Workaround:

A valid workaround is to introduce a new editor definition using the mirror registry as needed. This can include copying the defaults explicitly and merely updating their image references.

Prerequisites (if any, like setup, operators/versions):

Issue seems to affect all versions of Dev Spaces >= 1.15, where the feature to create custom editor definitions was introduced.

Steps to Reproduce

1. Install Dev Spaces to cluster
2. Create and modify the default CheCluster object such that:

spec:
  containerRegistry:
    hostname: <mirror-registry-hostname>

3. Spin up workspace using a default editor
 

Actual results:

Most Dev Spaces images (such as the project-clone container) use the mirror registry, but actual editor images still use the Red Hat registry.

Expected results:

All images, including editor images, use the mirror registry.

Reproducibility (Always/Intermittent/Only Once):

Always

Acceptance criteria: 

Definition of Done:

Configuring the `.spec.containerRegistry` in the CheCluster object automatically configures default editor images as well. Workspaces launching with a default editor will use the configured mirror registry and not the Red Hat catalog.