Add config validations to each template that runs in CI

[blmalone]

Per this comment.

Got it, thank you. Another type of test we should have if we don't have it already, is config files of real templates. For example, we can have a ProtocolVersionsUpdate template, and a test config file specifies some random version strings to upgrade too. The ProtocolVersionsUpdate solidity template has validations, and CI runs the test config files for these real templates. This gives us confidence that our templates are always working and pass the validations

Permanently running them in CI because they're templates, that way we know templates always work and pass the assertions.

---

Our current regression tests use an older block. We want to make sure our templates are always useable from the latest block. By running a simulation from the task directory we can make sure the latest block is always used.

src/improvements/tasks/example/*:
- we have TOML files and .env file and README.md
- keep these as non terminal
- Have one example per template make sure it runs in CI.