feat: config versions

[strophy]

Store version of package.json used to create a config, and check that version against current package.json version during config validation.

Issue being fixed or feature implemented

This means it will no longer be necessary to drop config and start again when new versions are released.

What was done?

Added a version to the config file schema and constructor, and check that version against the current package.json version to allow for transformations (yet to be defined) to the config as new settings are added.

How Has This Been Tested?

Tested in debugger and by looking at the generated file. Validation works and the conditional code is triggered.

Breaking Changes

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated relevant unit/integration/functional/e2e tests
• I have made corresponding changes to the documentation

For repository code-owners and collaborators only

• I have assigned this pull request to a milestone

[shumkov]

Good job! 👍