This will make e2e testing that requires and erc20
token that is mintable easy. Just send eth to the
correct address and then you will have an erc20
token.

This will be used for e2e tests for token deposits
and withdrawals.

The batch queue was using the previous origin when computing if
the origin was behind or not. It would then immediately advance
it's internal origin to the next origin (confusingly coming from
the `prev` stage). It would take action on the current origin based
on out of date data. Specifically, it would not save an origin that
should have been saved into the l1Blocks array. This causes errors
because the L1 Origin of the safe head would not be present when
attempting to derive the next batch after a reset.

The function signature wasn't updated with the arguments.

proxyd: Allow disabling backend rate limiting

proxyd: Support pattern matching in origin and user agent

Adds support for pattern matchin in exempt origins. This should help with some of the issues Synthetix and others are seeing.

op-e2e: action testing batcher actor

op-node: Allow *types.Block to satisfy the BlockInfo interface

op-node: Use DoCtx in DialRPClientWithBackoff

op-e2e: action testing user

There was a single usage of BlockInfo.ID() which I replaced with
a function called `ToBlockID` which can take either a BlockInfo
or a types.Block (it uses an interface consisting of Hash and NumberU64).

This fixes an issue where if a short context was supplied to the call it
would still take a long time to complete.

The backend rate limiter is in place to protect upstreams like the sequencer. However, in many cases it isn't needed and it causes unnecessary requests to Redis. This PR allows this to be disabled, and disables this by default.

Version Packages

Develop -> Master

proxyd: Integrate custom rate limiter

proxyd: Custom rate limiter implementation

Both op mainnet and op goerli

The following script was used for the deployment.
The commented out lines were used for mainnet.

```bash

NETWORK=optimism-goerli

npx hardhat deploy --network $NETWORK --tags MintManager
```

The L2 head was being logged rather than the safe head's L1 origin.

The handler returned from `log.LvlFilterHandler` wasn't being consumed anywhere, so log level configuration was being ignored.
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

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: add optional data field to RPCError struct

* fix: formatting lint

* feat(proxyd): add changeset

fix(ctb): remove unnecessary L2OO init param