**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
#
#
import re
import sys
import unittest
from shutil import copyfile, copytree
from tempfile import TemporaryDirectory
import jmespath
import pytest
from parameterized import parameterized
from tests.helm_template_generator import render_chart
class PodTemplateFileTest(unittest.TestCase):
    @classmethod
    @pytest.fixture(autouse=True, scope="class")
    def isolate_chart(cls):
        with TemporaryDirectory() as tmp_dir:
            cls.temp_chart_dir = tmp_dir + "/chart"
            copytree(sys.path[0], cls.temp_chart_dir)
            copyfile(
                cls.temp_chart_dir + "/files/pod-template-file.kubernetes-helm-yaml",
                cls.temp_chart_dir + "/templates/pod-template-file.yaml",
            )
            yield
    def test_should_work(self):