Add a CI job to "tidy" all the config files

[geoknee]

This is to keep the formatting strictly adhered to.

It should be a local tool which overwrites the raw config yml files using the Go bindings/types. This way it will serve as a double check on our marshalling / unmarshaling code.

We then run the tool in CI and run git diff --exit-code.

Should we make a CI job to "tidy" all the config files, to keep the formatting strictly adhered to?

Originally posted by @geoknee in #279 (comment)

[geoknee]

This job can also enforce that superchain_level: 2 and standard_chain_candidate = true should not both appear in a config file.