* op-e2e: Start adopting op-chain-ops

This PR starts the process of adopting op-chain-ops in op-e2e by porting over the `Secrets` struct we use in Hive. This lets us share wallet generation code among different projects.

Adopting op-chain-ops in op-e2e improves the following:

1. Transactions now route through the correct proxy contracts.
2. There's no need to wait for a contract deployment since conracts exist in genesis.
3. We can export the test helpers in op-e2e to enable us to run similar end-to-end tests in other applications like the indexer

This is the first in a series of stacked PRs.

* op-e2e: Migrate tests to op-chain-ops

* Updates from code review

* remove unnecessary method

* Update op-e2e/setup.go
Co-authored-by: Joshua Gutow <jgutow@optimism.io>

* CR updates

* Update op-e2e/e2eutils/secrets.go
Co-authored-by: Joshua Gutow <jgutow@optimism.io>

* Update op-e2e/e2eutils/secrets.go
Co-authored-by: Joshua Gutow <jgutow@optimism.io>

* try to fix test timeout

* fix deadlock

* fix similar case
Co-authored-by: Joshua Gutow <jgutow@optimism.io>

--wip--

wip

Adds the test key used in geth's unit tests to the genesis
alloc. This makes testing more seamless when using the
op-chain-ops tooling
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

Check for nil values coming from the block when creating
a new `StorageConfig`. This will prevent cryptic errors
that happen deeper in serialization, when trying to
deal with `nil` values. Instead the error should be caught
earlier with a better error message.
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

For building a developer genesis, if the `L2Addresses` struct
is `nil`, it will now use the default values. This simplifies
config and reduces code duplication as `nil` can now be passed.
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

Improve the error message on failed deployments.
This will make it much easier to debug issues with config.
The name of the deployment will not be returned as part of the
error, along with the error message itself. This error
is likely due to a revert in the constructor or an out of gas
during deployment.
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

Co-authored-by: Matthew Slipper <me@matthewslipper.com>
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

* op-node: Clean up pipeline

Now that the engine queue is the only step stage, it is easy to
consolidate different loops inside the derivation pipeline.

* op-node: Fully remove the progress API

It has been partially replaced with the Origin API, but the open/closed
distinction no longer exists.
Co-authored-by: Matthew Slipper <me@matthewslipper.com>

Now we no longer need to use one off scripts for testing this kind
of thing. The hh task will check to see the status of a transaction
hash and then finalize the withdrawal on L1 if the message status
is ready for relay. It does this by creating a `CrossChainMessenger`.
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

This function was not being used and could be safely removed.
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

Integrates the HTTP PollingClient with the op-node. To do this, I needed to change the RPC interface to return an `ethereum.Subscription` object rather than a concrete *rpc.ClientSubscription instance. I also introduced a new method to return the correct `client.RPC` implementation based on the user's chosen RPC URL.

Lastly, I added an additional CircleCI job to run all end-to-end tests against an HTTP-based RPC endpoint to prevent issues from arising in the future.

The Geth RPC client does not support subscriptions for HTTP endpoints. As a result, users who set an HTTP endpoint for the op-node were unable to sync since the driver never got any L1 head updates. This PR adds a wrapper around `client.RPC` that makes `newHeads` subscriptions work over HTTP. It does this by layering a notifications system that mimicks what Geth does under the hood on top of an HTTP polling loop.

The interface is the same as the one exposed by the raw RPC client. I tried my best to match Geth's subscription semantics, including:

- Closing the client causes all subscribers to get a nil error on their error channels.
- Unsubscribing closes each subscriber's error channel.
- Calling `Unsubscribe` multiple times is safe.

The poll rate is configurable. It default to 250ms, which should be fine for both L1 and L2. I tried at first to use Geth's underlying libraries, but found that it was impossible to do so without making changes to Geth itself to export more fields. This system is also simpler, and gives us room to instrument the polling loop in the future.

The wrapper is not integrated with the rest of the system in this PR. I'll stack those changes on top of this one so we can review this in isolation.

Totally open to different solutions here - marking as draft to reflect the fact that if there's a better way to do this, I'm happy o close this + the dependent PRs and go a different route.

Meta:

- Fixes ENG-2490

* ci: Parallelize op-e2e

Replaces my previous PRs since `t.Parallel()` works fine. Also exposes the listener on the op-node, so that we can use a port of zero and allow the kernel to allocate a port.

* close other geth nodes

* missed one

* use t.cleanup

op-e2e: Action testing L2 Engine Block building

op-e2e: Action testing L2 engine (without block building)

* ctb: Remove unused event in tests

* ctb: Initial clean up of L1StdBridge tests

Breaks the test suite up in to test contracts. Each state changing
method has its own contract for happy tests and another for sad
tests.

* chore: Bindings
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

* ctp: deploy goerli nft bridge fixes

Test on kovan

* ctp: goerli nft bridge deployment artifacts

* ctp: delete kovan bridge artifacts

* ctp: revert deploy script

* ctp: add goerli nft bridge deployment changeset

Co-authored-by: Mark Tyneway <mark.tyneway@gmail.com>

* op-e2e: action testing L1 replica actor

* op-e2e: action testing L1 miner (#3607)

* op-e2e: remove unused empty actors file

Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

* op-node: ParseWithdrawalInitiated improvements

`ParseWithdrawalInitiated` used to pass every log to `abi.EventByID`. Since `abi.EventByID` was bound to the `L2ToL1MessagePasser` contract, any logs on the receipt from a different contract would cause this function to return an error. This breaks support for parsing withdrawal events initiated by the `L2StandardBridge`, since the bridge adds many events of its own. This PR updates `ParseWithdrawalInitiated` to use the hex-encoded withdrawal intiated topic to determine which log messages to use instead.

* add extension 1

* Update op-node/withdrawals/utils.go
Co-authored-by: protolambda <proto@protolambda.com>

* Update op-node/withdrawals/utils.go
Co-authored-by: protolambda <proto@protolambda.com>

* Update op-node/withdrawals/utils.go
Co-authored-by: protolambda <proto@protolambda.com>

* add docstring

* use shared lib
Co-authored-by: protolambda <proto@protolambda.com>
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

These changes make the `OptimismMintableERC721Factory` in line
with the bedrock version of the `OptimismMintableERC20Factory`.
We might as well follow what we are doing with the new erc20
factory to keep things in line with each other.

These changes are very small, they just rename a function to
not follow the deprecated naming scheme, the function now returns
an address which makes testing/integration a bit easier and also
does a slight refactor to prevent the need to cast a type 3 times.
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

Use the companion network config to ensure that the
correct artifact is being used.
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>