As discovered while solving CRW-2887, there's a disconnect between how we build the registries (including generated devfile content) and how we then create the RELATED_IMAGES references in the CSV.

In future, instead of regenerating registry content via the upstream build scripts to get image refs to inject into the CSV... https://github.com/redhat-developer/devspaces-images/blob/devspaces-3-rhel-8/devspaces-operator-bundle/build/scripts/insert-related-images-to-csv.sh#L55-L61

... we should:

• PULL latest registry images
• extract containers to disk
• use generated content directly

This way the image refs / yaml files used will come from the the exact same content / from the same commit SHA as the containers referenced in the operator.