Finalizer need to be removed if pod is terminating and 0 containers are running.

Sometimes we see a termination pod  with 0 containers running (e.g. 0/3, we have a few sidecars), however still has the kube-arangodb operator finalizer. 
This prevents k8s to delete the pod. I would suggest if the operator detects this scenario, it removes the finalizer, so a new pod can be created and the system can recover. 