Decouple from op-geth and op-node

[tynes]

See ethereum-optimism/op-geth#464

Sometimes we need to make a quick release of the software when a chain is launching by bumping the version of the superchain-registry that is pulled into the monorepo and op-geth. This is unsafe because there may be features that are not ready to be released yet that have been merged. If we decouple superchain-registry releases from the rest of the releases so that the latest superchain-registry release is pulled in via HTTP URL, then we no longer need to cut a release of the client software when there is a registry release.

This URL can be configurable with a default, so that users can serve their own if they don't want to trust the default source for configs.

[tynes]

After chatting with @mslipper about this, we decided that backporting new releases of the superchain-registry on top of older release of op-geth and op-node makes more sense for now. The problem with the absolutePrestate might sort of be fixed by using shared proof contracts, but it will not solve the problem between clusters