Currently, the ComplianceCheckResult object has a creation timestamp, but not an updatedAt timestamp. This makes it difficult to know when the last time a ComplianceCheckResult was updated, unless you assume all results are the latest and know to fetch the latest state from the parent scan.

We can make this easier for users by updating the ComplianceCheckResult to include an updatedAt timestamp or even using the status condition that are already present in other compliance operator resources.

This is necessary for ACS to consume compliance data from the compliance operator because it forces the CRD to update, which sensor will pickup and forward along to central.