feat(validation): add validation on plugin options

[nicojs]

A Stryker plugin is now able to contribute to the validation of StrykerOptions. Export a JSON schema from your plugin with the name strykerValidationSchema and it will be added to the validation.

Also some housekeeping: 🏡

• StrykerOptions now support additional options as [k: string]: unknown instead of [k: string: any. This added about 100 compiler errors that I had to fix.
• We apparently had some hidden features, like options for the clear text reporter and event recorder reporter. They are now documented in the core schema

Example:

$ npm run stryker

13:17:48 (24856) INFO ConfigReader Using stryker.conf.js
13:17:49 (24856) ERROR OptionsValidator Config option "mochaOptions['async-only']" has the wrong type. It should be a boolean, but was a string.
13:17:49 (24856) ERROR OptionsValidator Config option "tsconfig" has the wrong type. It should be a object, but was a string.
13:17:49 (24856) ERROR StrykerCli Please correct these configuration errors and try again.

TODO

• Add unit tests and integration tests
• Add an e2e test for some wrong config
• Remove additional logging from Ajv

[simondel]

Why don't you use a getter here?

[nicojs]

Yeah, I guess we could. Wanted to keep it in line with the other method. Also want to keep it open for us to do a dynamic search in the future.

[simondel]

aren't these objects? (a bit more strict than any)

[nicojs]

Yeah, but I didn't want to bother with trying to explain TypeScript that it has properties and definitions. I know they have them and it is a private API for the time being. Didn't want to waste time on writing code to validate that the schemas are valid json schemas.