Upload config files to a CDN on merge

[nitaliano]

Is your feature request related to a problem? Please describe.

Right now any products that we build that consume the superchain-registry will always require version bumps and new deployments of that software anytime a new chain gets added or a field gets updated. To me this registry and the config values are very similar to DNS and I believe we should also support of path of where new configs and chains can just propagate without needing to bump any versions anywhere.

Describe the solution you'd like

On merges to the main branch we could potentially start to upload all of the *.json & *.toml files to our CDN that lives on cloudflare https://static.optimism.io/ (example) currently only the tokenlist and any of our FE apps publish to it. This will allow people to fetch the information dynamically at a trusted source.

static.optimism.io/registry
- chainList.json
- chainList.toml
- config.json

Describe alternatives you've considered

Just hitting the raw github content URL but that means anytime Github goes down so will anything that depends on dynamic fetching of configs. We are doing this here in the new CLI we are building https://github.com/ethereum-optimism/super-cli/blob/10def81e144e7ac29148a6b9373f60e2e5a9fdcd/packages/cli/src/superchain-registry/fetchChainList.ts#L12