Automatically use productized version of k8s-image-puller, when imagePuller is specified in checluster CR

Since we can now specify imagePuller in checluster CR it would be nice, if  the image puller used in this case would be the productized one (https://catalog.redhat.com/software/containers/codeready-workspaces/imagepuller-rhel8/5e42db8ed70cc54b02bd7ed6) not the community one.

Furthermore I think it's not even possible to specify which k8s image puller image should be used leaving users no other option than to deploy k8s image puller applying the templates (https://access.redhat.com/documentation/en-us/red_hat_codeready_workspaces/2.6/html-single/administration_guide/index#installing-image-puller-on-openshift-using-openshift-templates_crw) if he wants to use the productized image of k8s-imagepuller.

Current situation is IMO bit chaotic and there are multiple possible resolutions:

• Don't have imagePuller in checluster CRD - this way, users would have to install imagepuller using templates

• Leave imagePuller and use upstream k8 image puller operator, but add there a parameter to be able to specify which image can be used (not possible now AFAIK). This would result in easy to use solution, but with weird combination of community & productized bits. (stretch goal - CRW operator woud use the productized k8s-imagepuller image by default)

• Productize the k8s image puller as well? IMO this would be the cleaniest solution, but I have no idea how doable this is (and what are all the consequences of productizing this)

If this gets somehow implemented, it will most likely affect docs as well.