Refactor rego for each baseline to include detailed message in report about scubagoggles HOT 2 CLOSED

Documenting the approach I used on #176:

1. I created a new function in the Utils file ReportDetails. Because it's in the Utils file, when implementing this change for other baselines, there won't be any need to implement this again.
2. For each control:
   a. Determine an appropriate SettingDescription for the setting in question
   b. Determine if the LastEvent.NewValue value is user-friendly; if not, create a GetFriendlyValuex_x function that translates the values to user-friendly strings (see #176 for examples)
   c. Refactor the NonCompliantOUsx_x rule so that it includes both "Name" and "Value" keys
   d. Change the ReportDetailsOUs call to ReportDetails (include the SettingDescription from step a)
   e. Test and ensure it works as expected
   f. Update the unit tests to reflect the change

Scenarios that aren't covered by the above workflow:

• Handling settings that aren't controlled at the OU level
• Controls that depend on multiple settings

from scubagoggles.

See #204 for how this would look post group bug fix.

from scubagoggles.