[Feature Request] Update `oscap` logic to allow use of a tailoring XML in concert with standard remediation

[ferricoxide]

Is your feature request related to a problem? Please describe.

The oscap content shipped as part to the overall watchmaker content contains more content than is executed in the default profile(s). It would improve hardening-flexibility to ensure that the oscap-invocations were written to be able to pass a site-specific tailoring file.

Describe the solution you'd like

Change oscap methods so that, instead of using just the relevant profile's default content, they include reference to tailoring-content …then make that tailoring-content null.