Description of problem:

In some situations, the policy framework will remove the compliance state in the status of policy templates (eg OperatorPolicy) in order to signal those policy controllers to send a new compliance event. Users should also be able to reset that status field for the same purpose. OperatorPolicies are not handling this situation correctly, generally ignoring the status update, and not emitting a new compliance event unless some other state on the cluster relevant to the policy had changed.

Version-Release number of selected component (if applicable): 

How reproducible:

Steps to Reproduce:

1. Create an operator policy and wait for it to become fully compliant.
2. Remove the `status.compliance` field
3. Observe whether a new status is present in the policy history.

Actual results:

No new status emitted when the compliance is reset.

Expected results:

A compliance event should be emitted when the compliance is reset.

Additional info:

Found during an investigation sparked by this Slack thread: https://redhat-internal.slack.com/archives/CU4QXLPQB/p1729087710673909