Feature-Request: Define PriorityClass in ComplianceSuite to have pods run with a specific PriorityClass

1. Proposed title of this feature request
Feature-Request: Define PriorityClass in ComplianceSuite to have pods run with a specific PriorityClass

2. What is the nature and description of the request?
When heavily using Pod Priority and Preemption as documented in https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md#how-does-cluster-autoscaler-work-with-pod-priority-and-preemption it becomes necessary to assign a PriorityClass to pods from the Compliance-Operator to run them with the required priority, to eventually even preempt other pods in order to run.

3. Why does the customer need this? (List the business requirements here)
When heavily using Pod Priority and Preemption for automated scaling and the default PriorityClass is too low to guarantee pods to run then scans are not executed and reports are missing. Since the Compliance Operator is required to run, it would be helpful to define the PriorityClass for all the pods created by the Compliance Operator to guarantee they are running (or the other way around, only run when capacity is available)

4. List any affected packages or components.
Compliance Operator