Compatibility between hyperGRC opencontrol format and compliance-masonry

[openprivacy]

hyperGRC extended the opencontrol file layout used by compliance-masonry to enable each component to have separate files for each control. Either:

1. a pull-request to compliance-masonry should be made that enables it to read in this alternate layout
2. a script should be created created that converts one format to the other
3. we should abandon this useful format

[JJediny]

Speaking for myself

But I'm finding it best to have a 1 to 1 ratio of a single yaml file for an entire component.yaml; the control families are arbitrary. When you assume most components at most have 20-30-40 controls relevant the file size isn't a factor. Its also helpful to read them all together to see how the text relates etc etc and that way taxonomy of filenames is never an issue.