Bug 1969845

Description of the problem:

Even though there are violations, the GRC dashboard shows no policy violations 

Release version: 2.2.3

# steps to reproduce:


1. create a new project: 
~~~
oc new-project scott-limit-test   (this one will have limits on it)
~~~
2. define the mem limit ranges in it: see the example here: https://kubernetes.io/docs/tasks/administer-cluster/manage-resources/memory-default-namespace/
~~~
oc apply -f https://k8s.io/examples/admin/resource/memory-defaults.yaml --namespace=scott-limit-test
~~~
3. create another new project: 
~~~
oc new-project scott-nolimit-test (this one will have NO limits on it)
~~~
4. create your mem limit range policy against the **local-cluster**
**notice** how I created mine to look at all scott-* namespaces, and, it matches the metadata name: mem-limit-range which is also what I used when defining the namespace mem limit (see example in #2 above)
~~~
  policy-templates:
    - objectDefinition:
        apiVersion: policy.open-cluster-management.io/v1
        kind: ConfigurationPolicy
        metadata:
          name: policy-limitrange-container-mem-limit-range
        spec:
          namespaceSelector:
            exclude:
              - kube-*
            include:
              - scott-*
          object-templates:
            - complianceType: musthave
              objectDefinition:
                apiVersion: v1
                kind: LimitRange
                metadata:
                  name: mem-limit-range
                spec:
                  limits:
                    - default:
                        memory: 512Mi
                      defaultRequest:
                        memory: 256Mi
                      type: Container
~~~
5. At this point you should refresh the policy page a few times and it will show as green Compliant.
6. Click on the mem limit policy you have created, then click on Status and click on View Details
7. You should see the green Compliant for the scott-limit-test   (this one will have limits on it) and you should see the red Non Compliant for the scott-nolimit-test (this one will have NO limits on it). These are both valid and correct.

# Expected results:
The overall status of the mem limit policy should be red Non compliant due to the non compliant scott-nolimit-test that was found.