When the custom batch serialization was being used instead of RLP, a
transaction being sent to `address(0)` was not allowed because that
meant that it was a contract creation because there is no abi encoding
for `nil`. To prevent collisions, transactions sent via RPC to
`address(0)` were banned. Now the RLP transactions are being used, this
check can be removed. It helps to reduce the diff from upstream geth.

l2geth: remove diffdb

l2geth: remove unnecessary reflect

l2geth: small changes to miner codepath

l2geth: small syntax fix in the syncservice

This PR removes the diffdb as it is not currently being used.
Removing the diffdb is meant to help with resource usage of the node.

Very minor fix to the syncservice

These are minor changes to the miner codepath.

l2geth: remove layer of indirection with state manager

Add hardhat task for withdrawing ETH fees

There was a usage of `refect` that was not required. This PR removes its
usage so that the code is simplified.

This PR removes the assignment of a pointer to the
state manager abi and just directly uses it instead.
There is an assumption that the state manager abi exists,
but this check happens at startup time, when the abis are
pulled from the state dump.

l2geth: update the start script to work with regenesis 0.4.0

Adding k8s api client to op_exporter

`scripts/start.sh` was never updated to work with the latest regenesis,
this should update it so that it does. I confirmed that the genesis
state roots do match when starting a node using this script and mainnet.

Update health handler to return version
Remove dead code, continue, return nil
Added ticker for k8s loop

fix: estimate gas when pending tx in mempool

style: address pr feedback

chore(deps): bump tar from 4.4.13 to 4.4.15

contracts: add hardhat task for whitelisting addresses

This PR adds a hardhat task for whitelisting addresses. It can be used like so:

```
$ npx hardhat whitelist --address 0x.. --use-ledger true --contracts-rpc-url https://...
```

Bumps [tar](https://github.com/npm/node-tar) from 4.4.13 to 4.4.15.
- [Release notes](https://github.com/npm/node-tar/releases)
- [Changelog](https://github.com/npm/node-tar/blob/main/CHANGELOG.md)
- [Commits](https://github.com/npm/node-tar/compare/v4.4.13...v4.4.15)

---
updated-dependencies:
- dependency-name: tar
  dependency-type: indirect
...
Signed-off-by: dependabot[bot] <support@github.com>

feat: migrate and refactor replica-healthcheck from op-replica

l2geth: make block hashes deterministic

The blockhashes can be non deterministic because there is not a global
consensus in the existing deployment of the optimism network, instead
each node runs with `--dev 0` meaning that it auto mines transactions
itself. Previously, block hashes were non deterministic due to a
different clique signing key being used but that was fixed so that
a deterministic key is used for all nodes.

This fixes the possibility of the block extradata being different which
would result in different block hashes. The extradata is hard coded
to be the same value as the release @eth-optimism/l2geth@0.4.6. In
version 0.4.7, the underlying Dockerfile pulled in a patch release of
the Go runtime which caused the extradata field to become different.
The extradata field by default is the version of the software (which
cannot change until the next regenesis), "geth", the go runtime version
and the operating system.

This will require a resync to make block hashes deterministic across the
network.

l2geth: fee too high error message

Version Packages

Update the error message returned when the fee is too
high to return the correct multiplication. It should be
the expected fee * the fee threshold up.

Develop -> Master PR

fix[smock]: add naive support for packed storage slots

Add logging advice to /ops/README.md to avoid disk exhaustion problems

fix(l2geth): revert rpcGasCap logic to upstream geth behavior