Validate configuration objects

[amondal2]

Before pushing task configurations to Azure, they should be validated against the latest schema using the validation service/API. Should include a bypass flag for local development.

[amondal2]

From EDAV: "The app domain and cert is set, however we are working with RAST team to install CDC cert on VAP to be able to get to the app."

This should wait until the proper certs and config is done for the validation service so it can be called from GHA/VAP.

[amondal2]

@natemcintosh @zsusswein where do you think we should validate the configs against a schema? My thought is at the beginning of the orchestrate_pipeline function in cfa-epinow2-pipeline here, but am open to other ideas

[natemcintosh]

That would be a good place to do it. The read_json_into_config() function will also provide basic validation by causing the pipeline to error out if any of the fields in Config are missing, minus the optional_fields. The optional fields are currently just "exclusions"; all other missing fields will result in a crash.