v4.2.1: initContainer fails to start when using multiple custom schema "files"

[zoc]

Describe the bug
When several custom schema files are defined, the volume mounts of the init container contains several times the same mount, preventing the container from starting. Example in my case (see custom-schema-files mount being repeated multiple times with the same mount path):

      volumeMounts:
        - name: cm-custom-schema-files
          mountPath: /cm-schemas/00-overlays.ldif
          subPath: 00-overlays.ldif
        - name: custom-schema-files
          mountPath: /custom-schemas/
        - name: cm-custom-schema-files
          mountPath: /cm-schemas/dnszone.ldif
          subPath: dnszone.ldif
        - name: custom-schema-files
          mountPath: /custom-schemas/
        - name: cm-custom-schema-files
          mountPath: /cm-schemas/postfix.ldif
          subPath: postfix.ldif
        - name: custom-schema-files
          mountPath: /custom-schemas/
        - name: cm-custom-schema-files
          mountPath: /cm-schemas/rfc2307bis.ldif
          subPath: rfc2307bis.ldif
        - name: custom-schema-files
          mountPath: /custom-schemas/
        - name: cm-custom-ldif-files
          mountPath: /cm-ldifs/
        - name: custom-ldif-files
          mountPath: /custom-ldifs/
        - name: cm-replication-acls
          mountPath: "/cm-schemas-acls"
        - name: replication-acls
          mountPath: "/custom_config"

Expected behavior
Only one custom-schema-files mount should be present.

Screenshots
N/A

Desktop (please complete the following information):
N/A

Smartphone (please complete the following information):
N/A

Additional context
N/A