Add Compliance Operator to pattern and enable in hub cluster

[masalowitz]

Changelog:

• Add namespace, subscription, and operator chart location for Compliance Operator to values-hub.yaml
• Create chart location for compliance-operator under charts/hub/compliance-operator
• Added default chart stubs
• Added templates for ScanSettingBindings for ocp4-high, ocp4-node-high, and rhcos4-high NIST content
• Added additional generated unit tests from pattern.sh output
• Tested on 4.11 and 4.12

[beekhof]

@day0hero this seems like a nice improvement, any reason we shouldn't merge this? should it be on all deployments or is it more an optional thing?