When integrating the Compliance Operator with ACS, it's impossible for the ACS central component to guarantee it received all the ComplianceCheckResults for a DONE scan.

The problem is that each update to the ComplianceCheckResult and ComplianceScan objects are sent to the central cluster by sensor. ACS doesn't know how long it should continue waiting for ComplianceCheckResults after it receives an update that the ComplianceScan is complete.

One way to fix this would be to implement a total check count as an attribute of the ComplianceScan. When ACS receives the update that a scan is done, it also receives the number of expected ComplianceCheckResults that should be coming in as part of that update.

This makes it so that ACS can definitively say a scan is complete.