Use toml instead of yaml for chain config files

[bitwiseguy]

Description

Instead of using a combination of toml, yaml, and json config files, this PR combines the old config yaml, addresses json, and genesis-system-config json into a single toml file. This should make it easier to maintain thesuperchain package bindings going forward. There are already rust and go bindings for that package, but it will also be easier to add other languages in the future.

There are no breaking changes for downstream packages (i.e. op-geth and op-node) introduced by this PR. Instead, the superchain package init() function has just been updated so that it can parse the single toml config file and then populate the same data structures that were exported before.

Additional Context

Fixes #285

[geoknee]

This is looking pretty good to me so far, left a few comments.

[geoknee]

The codegen functionality / check will break when we delete the extra addresses json files.

We should migrate codegen.js

superchain-registry/scripts/codegen.js

Lines 7 to 11 in 5d2f856

	/**
	* Geneartes the addresses.json file that sits at the root of the
	* superchain/extra/addresses folder. Useful to have a combined JSON file for
	* all of the various addresses to avoid dynamic imports.
	*/

to be performed by the existing Go codegen tool:

superchain-registry/superchain/internal/codegen/main.go

Lines 33 to 34 in 5d2f856

	func main() {
	allChains := make([]ChainEntry, 0)

I think we have all of the utility code we need to do that.

Finally, we would trim the node codegen.js line from the justfile.

[refcell]

Rust code GTG. go LGTM.