client [NET-992]: pre-compiled JSON schema validator

[harbu]

Summary

Compile JSON schema validator functions at build time instead of run time as described here https://ajv.js.org/standalone.html to avoid having to rely on eval during run time. Another added benefit is that we don't need to include ajv in our webpack build, reducing the browser bundle size slightly.

Changes

• Mark packages ajv and ajv-format as dev dependencies.
• Add script bin/generate-config-validator.js that generates the pre-built JSON schema validator function.
• Call above script in prebuild phase, ensuring it gets called every time the client package is built.
• Add folder src/generated for generated code that gets ignored by eslint.

Checklist before requesting a review

• Is this a breaking change? If it is, be clear in summary.
• Read through code myself one more time.
• Make sure any and all TODO comments left behind are meant to be left in.
• Has reasonable passing test coverage?
• Updated changelog if applicable.
• Updated documentation if applicable.

[linear]

NET-992 Compile schemas at build time to avoid eval with ajv

This ajv dependency is giving trouble to Swash, because it uses eval which is now completely forbidden in Chrome webstore. Apparently this library is related to schema validation. On the ajv website there's this note:

In order to use Ajv without relaxing CSP, you can compile the schemas using CLI (opens new window) or programmatically in your build code - see Standalone validation code. Compiled JavaScript file can export one or several validation functions that have the same code as the schemas compiled at runtime.

If I understand correctly, instead of using the library at runtime (which involves the evil eval), it's possible to compile the schemas at build-time and thus completely fix the issue.