Disable Registry Scan feature for flux

There are a lot of error messages in the Flux pod. They are caused by Flux checking for new images, but access to container registry is not provided: https://fluxcd.io/legacy/flux/faq/#how-do-i-give-flux-access-to-an-image-registry Flux transparently looks at the image pull secrets that you attach to workloads and service accounts, and thereby uses the same credentials that Kubernetes uses for pulling each image. In general, if your pods are running, then Kubernetes has pulled the images, and Flux should be able to access them too.

Since we do not use this feature, it can be disabled. https://fluxcd.io/legacy/flux/faq/#can-i-disable-flux-registry-scanning