Be sure to switch to using the new rules
at a specific height

The implementation is copied from upstream
https://github.com/ethereum/go-ethereum/commit/a5669ae292274d3b0a223cda07ebe64f943bded4

fix

Add in the berlin precompile maps. This code is adopted from
upstream.

This includes the implementation of EIP-2565 which
makes the modular exponentiation precompile found
at `address(5)` cheaper.

https://eips.ethereum.org/EIPS/eip-2565

The berlin precompile set includes setting the `eip2565`
field to true on the `bigExpMod` struct.

This implementation is directly taken from upstream.
https://github.com/ethereum/go-ethereum/commit/eb21c652c0a9d8f651efc0251cc5797a3328d863

bss: split up SubmitBatchTx method in Driver iface

Previously it was being logged every time we modified the gas price.
Additionally, we log the raw byte length rather than tx.Size(). The
latter returns a float value of type StorageSize, which explains why the
metrics haven't been indicating actual byte values.

The current interface supports only one method for both crafting and
publishing a batch transaction, SubmitBatchTx. Currently this is being
executed on each new gas price that the txmgr commands, implying we are
doing a lot of extra work to rederive batches. In addition, much our
instrumentation lives inside this method, meaning that the they are also
being recorded multiple times per transaction. When we get to
processing larger batches on Kovan and Mainnet, this could also become a
resource bottleneck.

This commit remedies all of the above issues by splitting out the
transaction crafting process from the publication. A new method,
CraftBatchTx, is added to the Driver interface. This method is
responsible for creating a fully formed transaction, but does not
publish it. The responsibility of SubmitBatchTx is now modified to take
an predefined transaction, i.e. created by CraftBatchTx, overwrite the
supplied gas price, and publish. In this way, this expensive call to
build batches can be done once before handing the transaction of the
txmgr.

fix(batch-submitter): clear state root batches

Fixes a bug where both the sequencer and proposer main loops were
attempting to clear the pending transactions from the batch-tx
submitter's wallet. The impact is that we may have been overspending on
fees due to conflicting/reverting state batches. However the impact
overall should be minor given the relative size of state batches in
comparison to tx-batches.

feat: implement clear pending txs for go batch submitter

feat: L2Provider test scaffold

feat(proxyd): Support immutable RPC caching 

Makes sure that the Default sender is address(0)

feat: add BatchPruneCount metric