1. Proposed title of this feature request
Violations-as-policy

2. What is the nature and description of the request?

After a CNCF meetup, I recieved feedback from a few banking SREs that like the policy as code workflow and suggested a few feautures to simplify the workflow. Users wanted the following:

1. The ability to refuse the default policies/delete them and the ability to bring them back if they wanted. 
2. The ability to set a repository that RHACS pulls from to create "locally managed" policies quickly. This can be done by adding pull capabilities to the "import policy" feature. 
3. Users wanted YAML importing options.
4. Exported policies should have a YAML option.
5. When selecting "exclude deployment from policy" in the violations tab, users wanted the ability to export an updated policy/add reasoning to the exclusion. This was to add context in case of an audit later on and simplify the exporting workflow. 

3. Why does the customer need this? (List the business requirements here)

Not a customer. A suggestion based on community feedback.

4. List any affected packages or components.