Integrates the custom rate limiter in the previous PR into the rest of the application. Also takes the opportunity to clean up how we instantiate Redis clients so that we can share them among multiple different services.

There are some config changes in this PR. Specifically, you must specify a `base_rate` and `base_interval` in the rate limit config.

Our current proxyd deployment does not share rate limit state across multiple servers within a backend group. This means that rate limits on the public endpoint are artifically high.

This PR adds a Redis-based rate limiter to fix this problem. While our current rate limiting library (github.com/sethvargo/go-limiter) _does_ support Redis, the client library it uses is not type safe, is less performant, and would require us to update the other places we use Redis. To avoid these issues, I created a simple rate limiting interface with both Redis and memory backend.

Note that this PR only adds the new implementations - it does not integrate them with the rest of the codebase. I'll do that in a separate PR to make review easier.

fix(ctb): remove unnecessary L2OO init param

Removes an unnecessary parameter from the L200 initialization function
since this parameter is already set in the constructor.

op-node: Fillbytes size check in l1 block info

Add balance metrics to op-propose & op-batcher

This was done to test the addition of the balance metric.

This function periodically records the balance of the supplied
account through metrics. The balance is recorded in Ether (not wei)
to stay in bounds of a float64.

contracts-governance: allow deploy by ledger

Adds the config for using a ledger with hardhat
deploy. The env var `LEDGER_ADDRESS` must be
set for this to work.

Note that hh deploy is buggy and will always
use the default path when creating a `LedgerSigner`.
This means the `LEDGER_ADDRESS` env var is useless,
it won't actually use that address when doing a
deployment. Basically, if its set then it just means
use the ledger's first derived address at the default
path.

This should be an easy thing to fix upstream, although
kind of annoying. The paths would need to be searched
linearly until a matching address is found, I think
a better way to configure this is pass either:

- A path + address
- A path

If both are passed, then it should validate that the
path matches the address. If a path is passed, then
yolo use the derived account.

contracts-governance: mint manager deploy

op-node: make rollup node RPC testable in op-e2e

Include clear instructions for the upgrade transaction
that is not managed by this deploy script.

Add a deploy script for the new mint manager. To review this,
check the `cast` calls in the mint manager implementation
deploy script. The owners of the `MintManager` are preserved,
double check that in the `deploy-config` directory against
what the cast calls return.

To deploy this, the new implementation needs to be deployed
and then the existing owner of the `MintManager` needs to
send a transaction to the `MintManager` calling `upgrade(address)`
to the new implementation of the `MintManager`.

ctb: Format forge tests with prettier

fix: update goerli scc address

op-e2e: action testing L2 sequencer, use L1State in verifier

ctb: Fix codecov flag args to match config