**What happened**:

When you have `dag.persistence` enabled and a `dag.gitSync.sshKeySecret` set, the gitSync container isn't added to the pod_template_file for k8s workers, as expected. However, `volumes` for it still are and maybe worse, the ssh key is mounted into the Airflow worker.

**What you expected to happen**:

When using `dag.persistence` and a `dag.gitSync.sshKeySecret`, nothing gitsync related is added to the k8s workers.

**How to reproduce it**:

Deploy the helm chart with `dag.persistence` enabled and a `dag.gitSync.sshKeySecret`.

e.g:
```
dags:
  persistence:
    enabled: true
  gitSync:
    enabled: true
    repo: {some_repo}
    sshKeySecret: my-gitsync-secret
extraSecrets:
  'my-gitsync-secret':
    data: |
      gitSshKey: {base_64_private_key}
```

**Anything else we need to know**:

After a quick look at CeleryExecutor workers, I don't think they are impacted, but worth double checking.
chart/tests/test_pod_template_file.py
]
                        }
                    }
                },
                "tolerations": [
                    {"key": "dynamic-pods", "operator": "Equal", "value": "true", "effect": "NoSchedule"}
                ],
                "nodeSelector": {"diskType": "ssd"},
            },
            show_only=["templates/pod-template-file.yaml"],
            chart_dir=self.temp_chart_dir,
        )
        assert re.search("Pod", docs[0]["kind"])
        assert "foo" == jmespath.search(
            "spec.affinity.nodeAffinity."
            "requiredDuringSchedulingIgnoredDuringExecution."
            "nodeSelectorTerms[0]."
            "matchExpressions[0]."
            "key",
            docs[0],
        )
        assert "ssd" == jmespath.search(
            "spec.nodeSelector.diskType",
            docs[0],
        )
        assert "dynamic-pods" == jmespath.search(
            "spec.tolerations[0].key",
            docs[0],
        )
    def test_should_add_fsgroup_to_the_pod_template(self):