1. Implement LimitQueue, a max Priority Queue on StatusViolations which only hold items up to a certain limit L. Because the size is bounded by a constant limit, LimitQueue operations provide O(1) time complexity guarantees for all operations. The data structure only uses constant space so will not affect the audit manager's RAM usage.
2. Unit test LimitQueue and SVQueue classes to verify functionality.
3. Use LimitQueue as the value in the updateLists map instead of []updateListEntry so we can store audit results in sorted order up to constraintViolationsLimit.
4. Remove the intermediate type updateListEntry in favor of saving the StatusViolation directly. The only difference between the two is that updateListEntry used util.EnforcementAction while StatusViolation uses string. Update logViolation to log a string enforcement action. Keep the same logic to track totalViolationsPerEnforcementAction.
5. Move some variable definitions closer to where they will be used, for example details, labels, uid, and rv.

Signed-off-by: Prachi Pendse <prachirp@google.com>

…sults in sorted order

Signed-off-by: Prachi Pendse <prachirp@google.com>

Signed-off-by: Prachi Pendse <prachirp@google.com>