Use static secrets and keys

Argo is frequently checking cluster deployed resources with it's templates. When ArgoCD deployed application template expires, a new one is created and some secrets that are not static are regenerated triggering a new deployment of most of all components.

Similar thing will happen when we update resources that do not directly interact with harbor helm manifests.

Closes: https://gitlab.cern.ch/kubernetes/automation/releases/kops-registry/-/issues/36