Currently it is not possible to differentiate `che_plugin_sidecar_plugin_registry_image` from the RELATED_IMAGEs

Is your enhancement related to a problem? Please describe.

CSV contains a bunch of the che_plugin_sidecar_plugin_registry_image Related Images - https://github.com/operator-framework/community-operators/blob/b560ec81cd4e586e9cb05c3674426da4971ba3b3/community-operators/eclipse-che/7.32.0/eclipse-che.v7.32.0.clusterserviceversion.yaml#L1029-L1079

This becomes a problem if we want to automatically pre-pull by default some of the sidecar images e.g. java8 Currently, it is simply not possible to differentiate those, since all of them are using the same image names and different digests, and it is only possible to identify by tag names - https://quay.io/repository/eclipse/che-plugin-sidecar?tag=latest&tab=tags

Describe the solution you’d like

It should be possible to differentiate in the CSV che_plugin_sidecar_plugin_registry_image

Describe alternatives you’ve considered

Not pre-pull sidecar images at all by default

Additional context

This issue is related to https://github.com/eclipse/che/issues/19657

[tolusha]

Theoretically we can include image tag in RELATED_IMAGE env var name like this: RELATED_IMAGE_che_plugin_sidecar_plugin_registry_image_java8_1273116_<....> Will it fit your needs?

[che-bot]

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.