[BUG] config-manager does not respect global registry

[shanshanying]

KubeBlocks: 1.0.2
kbcli: 1.0.0

For deploy KubeBlocks with registryConfig:

  registryConfig:
    defaultNamespace: apecloud
    defaultRegistry:  some-registry-other-than-docker.io

Then create a mysql cluster, and we noticed that the config-manger image is still from docker.io

k get its mysql-cluster-mysql -oyaml | yq '.spec.template.spec.containers[].image'
some-registry-other-than-docker.io/apecloud/mysql:8.0.35
some-registry-other-than-docker.io/apecloud/mysqld-exporter:0.15.1
some-registry-other-than-docker.io/apecloud/mysql:8.0.35
some-registry-other-than-docker.io/apecloud/mysql:8.0.44  # config-manager

Soon, it changes to

some-registry-other-than-docker.io/apecloud/mysql:8.0.35
some-registry-other-than-docker.io/apecloud/mysqld-exporter:0.15.1
some-registry-other-than-docker.io/apecloud/mysql:8.0.35
docker.io/apecloud/mysql:8.0.44   # config-manager

[shanshanying]

Check RunningWorkLoad , its image is changed to docker.io by ComponentReloadSidecarTransformer

[cjc7373]

maybe related to #10034, i'll check with @kizuna-lek