[ Feature Branch ] Genesis allocs validation

[geoknee]

• Modifies add-chain flow to store sufficient metadata to validate the allocs in a chain's genesis file
• Adds a genesis package under the validation module, which contains a test to perform full genesis allocs validation
  • It does this by cloning the monorepo, checking out the declared commit, building and generating the l2 genesis using the deploy-config as input. The test can handle multiple different node versions, go versions, and genesis command invocations
  • This full check is only triggered if the validation metadata for a given chain is modified
  • The check is seperate from the other validation checks, so has its own triggers and conditions
  • For each chain modified in this way, we generate a dynamic CI configuration to run the validations concurrently, and then report a single "fan-in" result requiring all to pass
• Adds a "lite" check for each chain, run as a part of the regular validation suite, which requires the chain has a "genesis creation commit" stored for it.
• Adds validation metadata for several chains already in the registry, as well as some not yet in the registry (this allows us to save that metadata so we can use it later).

Closes #486
Closes #372
Towards #478

[geoknee]

Action plan:

• Merge the stack of PRs into this one.
• Rebase or update this PR
• Confirm all known chains still validate correctly
• Separate out any new chains being added on this PR, to get a streamlined version which only commits
  i. the add-chain code
  ii. the validation code itselg
  iii. the validation input files (meta.toml and deploy-config.toml)
• We save the new chain information onto another feature branch which we can continue to use to validate all of the chains we care about until they have been merged to main in the usual way

[bitwiseguy]

🚀