Decouple Superchain Registry

[tynes]

We sometimes need to make quick releases of op-geth because a new chain was added to the superchain-registry. This can be unsafe and create weird dependencies across different teams. We should decouple the superchain-registry as a dependency to fix this issue. One easy way to do this is to do releases of the registry similarly to how we do releases of the smart contracts and then allow for a CLI flag pointing to the appropriate config accept both a file on the local fs and also a remote HTTP URL. Then we can release the superchain-registry without needing to update op-geth.

The same issue can also result in a different absolutePrestate being created depending on an updated superchain-registry. The solution proposed here will not fix the problem for the proof, see ethereum-optimism/design-docs#153 and ethereum-optimism/design-docs#161.

[tynes]

Closing this due, will use backporting instead