* 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>

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

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

Version Packages

Develop -> Master

* op-e2e/actions: action tests base test util

* actions: extend action testing doc comments

* actions: docstring about format and args
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

op-node: Switch L1 Traversal to a pull based model

op-node: Switch L1 Retrieval to pull based

op-node: Switch channel bank and channel in reader to a pull based stage

op-node: Switch batch queue to be pull based

The progress API is very nearly removed from the engine queue stage.

The attributes queue actually had pretty few modifications to work
with the progress API. The logic of switching the batch queue over
was a bit more complex because the batch queue is very stateful, but
still not the worst.

Like the rest of the changes, this also required modifications to
the next stage - the batch queue in order for it to manage the
progress API. This commit required even more changes than usual.
I changed the pipeline to be reset to a common starting point
and now use the L2SafeHead block to filter out adding batches &
L1 blocks to the batch queue.

This again requires a fair amount of changes to channel_in_reader.go
for the channel in reader to maintain its progress state.

* ctp: fixup deploy scripts for the nft bridge

The most important one is the deploy script for the
`Proxy` that will end up at the predeploy on L2. There
are specific checks for the correct deployer account
being used. Will likely require some changes to the
hardhat config when doing the actual deployment.

* ctp: update deploy scripts

* ctp: update deploy scripts

* ctp: move away from deterministic deployments

* op: deployments

* fixes

* deploy-script: refactor

* deploy: comments

The L1 Retrieval stage is now responsible for pulling data from
the L1 Traversal stage. In addition, the pipeline is responsible
for advancing the state of the L1 Traversal stage.

The L1 Traversal stage only provides access to the current L1 block
once - it pretends to be a queue that is consumed from.

This makes the L1 Retrieval a purely pull based stage. This commit
required large modifications to the channel bank stage in order
for the channel bank to maintain it's own progress.

`check-changed` fails on stacked PRs. This PR updated the CircleCI config to simply run tests if check-changed fails in order to prevent PRs from getting blocked.

This new name is more idiomatic in go and avoids a confusion with
the '642'.

Removes refunds for failed NFT deposits.
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>