Add schema to configs

[flcl42]

Changes

• Add schema to chain configs, so it autocompletes

Types of changes

What types of changes does your code introduce?

• Bugfix (a non-breaking change that fixes an issue)
• New feature (a non-breaking change that adds functionality)
• Breaking change (a change that causes existing functionality not to work as expected)
• Optimization
• Refactoring
• Documentation update
• Build-related changes
• Other: Dev experience

Testing

Requires testing

• Yes
• No

If yes, did you write tests?

• Yes
• No

Out of scope:

• schema for the chainspecs
• test configs for correctness according to the schema
• gh action to update the configs

[LukaszRozmej]

Should we regenerate schema automatically on some build actions? Maybe the same one that updates pivots?

[flcl42]

Should we regenerate schema automatically on some build actions? Maybe the same one that updates pivots?

Yeah, a good idea. And we can push it to a repo, change link to absolute github url, so it will become accessible everywhere outside of the solution

[rubo]

• There are build errors because of the PowerShell script
• Also, the requirement of the PowerShell fails the build for those who don't have it
• Must have been added to the build-tools.yml to catch such errors