Temporary switch to new k8s secrets name

This is needed to we can easily migrate to the new db with the
recent pantry changes. If something goes wrong we can simply revert to
the old secret (and hence the old db).

Once the upgrade is done (and verified) we can update the old secret and
update the name in this commit (back to it's original name)

etc/helm/templates/cron_deployment.yaml

@@ -28,7 +28,7 @@ spec:
           - name: PGSTRING
             valueFrom:
               secretKeyRef:
-                name: {{ .Values.name }}
+                name: {{ .Values.name }}-upgrade
                 key: PGCONN
           command:
             - bash

etc/helm/templates/deployment.yaml

@@ -28,7 +28,7 @@ spec:
             - name: PGSTRING
               valueFrom:
                 secretKeyRef:
-                  name: {{ .Values.name }}
+                  name: {{ .Values.name }}-upgrade
                   key: PGCONN
           readinessProbe:
             httpGet:

etc/helm/templates/hoogle_deployment.yaml

@@ -28,7 +28,7 @@ spec:
             - name: PGSTRING
               valueFrom:
                 secretKeyRef:
-                  name: {{ .Values.name }}
+                  name: {{ .Values.name }}-upgrade
                   key: PGCONN
           readinessProbe:
             httpGet: