Support for schema validation of blueprintConfiguration objects

[scriptorian]

This PR has been opened by SuperFly.tv on behalf of EVS Broadcast Equipment.

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

Feature

What is the current behaviour? (You can also link to an open issue here)

When updating blueprintConfiguration objects through the REST API the new configuration is written to the database without any validation that the values conform to any schema.

What is the new behaviour (if this is a feature change)?

This feature supports blueprints that define blueprintConfiguration object JSON schemas and provides methods to support automatic, detailed validation of updated configurations against the published schema before being written to the database. Any invalid properties are reported back to the client.

Included is a small addition to the API that allows the blueprintConfiguration objects to be read and updated without including the rest of the studio or showStyle configuration properties.

Other information:

Status

• [x] PR is ready to be reviewed.
• [x] Code documentation for the relevant parts in the code have been added/updated by the PR author
• [x] No unit test changes are needed for this PR.
• [x] The functionality has been tested by the PR author

Affected Areas

• This PR affects the REST API implementation.
• Without blueprint changes there will be no change in behaviour.