Validate Notification `config.json` Schema Semantics

[nharper285]

We need to validate notification config files during job submission. Ideally, a user would attempt to deploy a job with a malformed json file and OneFuzz would immediately fail the job submission and return the failure to the user.

One potential solution would be to detail some kind of schema that can be used to check incoming configs against.

Validations we can add:

• Area Path exists in the project
• Iteration Path exists

AB#45445

[mgreisen]

I think what you're proposing here is sematic validation, right?

[tevoinea]

We had an initial start with semantic validation in PR: #2850 Issue: #994. Within ADO it:

• Checks if the PAT is valid
• Checks if the unique_fields in the config are valid for that ADO project

I'm sure we could extend the current validation with some more checks!