• Proposed title of this feature request:* {}Application set  with file generator should respect exclude directive.

• What is the nature and description of the request?

When we create an applicationset  using   git file generator, the application set does not exclude files.There seems to be a bug. We are using   openshift-gitops operator version 1.13.2.

• Why does the customer need this? (List the business requirements here)
  We are implementing Active/Active Argocd architecture. We would like to be able to specific config files from argocd applicationset generator One of the argoCDs are managing primary site and other one is managing DR site. 

Lets say our clusters are named ocpxx01, ocpxx02,..., ocpxx99  and ocpyy01, ocpyy02,..., ocpyy99. We are creating a  config file  for every cluster,   named "ocpxx01-config.yaml" and "ocpyy01-config.yaml"

We would like our primary application set to discover files named "*-config.yaml" on our git repository but should be able to exclude "*yy*-config.yaml". DR site applicationset should discover files "*-config.yaml" but should exclude "*yy*-config.yaml".

• How would the customer like to achieve this? (List the functional requirements here)
  For each functional requirement listed in question 4, specify how Red Hat
  and the customer can test to confirm the requirement is successfully implemented.

Creating an applicationset  and seeing that exclude directive works and application. Below manifests could be example:

kind: ApplicationSet
metadata:
  name: opensol-apps
spec:
  ignoreApplicationDifferences:
    - jsonPointers:
        - /spec/syncPolicy
  generators:
    - git:
        repoURL: gitrepo/appset-configs-test.git
        revision: HEAD
        files:
        - path: "./myapp/dev/*xx*-config.yaml"
        - path: "./myapp/dev/*yy*-config.yaml"
          exclude: true