fix secretKeyRef in web and worker deployment

while adding the possibility to use extistingSecrets I somehow managed to create invalid kubernetes resources but helm was not complaining, this should be the necessary fix (looks good locally).

Amazingly even argocd/the kubernetes cluster didn't complain, they did however also not create the proper resource, instead the settings from the existing secret were missing, and only the registries secret was added (maybe because it was the later defined name in the yaml)