added tests to ensure validator is working correctly when things chan…

[brenthosie]

…ge inside reactor-turbine-schemas

Description

Related Issue

Motivation and Context

When we make changes to https://github.com/adobe/reactor-turbine-schemas, we don't have a good way to validate those changes don't break existing manifest files. This provides a way to ensure our validator project, which is used in our open source tools and in our back-end processing services, still gives a thumbs-up on the changes to schemas.

How Has This Been Tested?

Added new structures in this project for unit testing.

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• I have signed the Adobe Open Source CLA.
• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.