TALM - precache does not begin if catalogsource config policy is Compliant

CGU now expects both catalogsource policy and subscription policy to be NonCompliant to begin precache. 

This expectation is correct for subscriptions, however, catalogsource index image might not change for operator upgrade. 
- For connected env, catalogsource index image does not change for z stream upgrade
- For disconnected env, customer can choose any index image that could have used same name/tag even for y stream upgrade. 

4.12

100%

1. config-policy containing catalogsource CR is compliant
2. subscriptions-policy containing subscriptions CR is NonCompliant with pending upgrade
3. start precache via CGU using above two policies

precache does not begin because catalogsource policy is Compliant

  - lastTransitionTime: "2022-12-09T23:51:08Z"
    message: No clusters available for remediation (Precaching failed)
    reason: Failed
    status: "False"
    type: Succeeded

CGU should not expect catalogsource policy to be NonCompliant for operator ugprade, especially for z stream upgrade.