Ignore differences in password secret when deploying postgres argocd app

[garryod]

Erroneous updates to this Secret were causing the password in the backend deployment to differ from that held by the postgres instance - unfortunately as ArgoCD performs a helm template followed by a kubectl apply the helm chart templates do not adequately avoid these updates