Volume static-files present and volumemount not referenced

[nunojusto]

Checklist:

• [ x] I've searched in the docs and FAQ for my answer: https://bit.ly/argocd-faq.
• [ x] I've included steps to reproduce the bug.

Describe the bug
I was backing up an ArgoCD instance with Velero and got an error with one volume defined in the argocd-server deployment, that does not have a mounted volume in any container.
That does not produce an error in kubernetes, but because velero/restic wants to backup that mount and it's not there, it gives an error.

So, I would say, if we have an old volume (from older manifests) that we don't use anymore, we should remove it.
I know it's an empty dir, but it's still not a best practice to keep it defined and not mounted.

You can see this here

argo-cd/manifests/base/server/argocd-server-deployment.yaml

Line 213 in aa6aed3

- emptyDir: {}

Expected behavior

Not having a volume defined and not mounted

Version

All install manifests