Add support for compensating control configuration as separate files

[basepi]

New top-level yaml key, control, which will be processed by hubble.py, not the hubble modules. Once the hubble modules return their results, hubble.py will inspect the failures for any that match any control config which was passed in as part of the run, moving those failures into the Controlled key instead.

This will allow targeting control configs by host via the topfile.

Potential format:

control:
  - CIS-4.1.2: We do not need this
  - CIS-2.3.5

Sample use in topfiles:

nova:
  '*':
    - CIS
  'web*':
    - control.webservers
  'db*':
    - control.databases