Finalize Configuration File Schema and Handling

Goal:

• We need to make final decisions about the config file format we'll go to GA with

Why is this important?

• The configuration file format is an API. We can change it, but making breaking changes requires extra effort to maintain backwards compatibility for some time. Settling on a format we can use and extend without making breaking changes will make maintenance and documentation easier.

Scenarios

• N/A

Dependencies (internal and external)

• None

Previous Work (Optional):

1. USHIFT-673
2. USHIFT-607
3. USHIFT-535
4. USHIFT-539
5. USHIFT-388
6. USHIFT-536
7. ETCD-317

Open questions:

• N/A

Done Checklist

• CI - MUST be running successfully with tests automated
• Release Enablement: <link to Feature Enablement Presentation> 
• DEV - Upstream code and tests merged: <link to meaningful PR orf GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>

DOC - Downstream documentation merged: <link to meaningful PR>