op-chain-ops: Improve OVM_ETH post check

Add how to use the SDK in OP Stack

feat(docs/op-stack): Slightly simpler installation

feat(docs/op-stack): @tremarkley 's autorefresh

op-chain-ops: Check and mutate DB in parallel during OVM_ETH migration

op-node: make find-sync-start more resilient against errors by improving cache usage

feat(ctb): Add negative test for token compliance in the `L2ERC721Bridge`

Improves OVM_ETH post-checks by sampling balances and making sure that they appear in state after the migration. Previously, the OVM_ETH post-check only verified that the total supply was set to zero.

Will test this on a fresh L2 migration.

Depends on #5198

Updates the precheck script to check and mutate the DB during the OVM_ETH migration. This saves a significant amount of time during the migration, since we avoid performing a full storage iteration over the OVM_ETH state followed by a single-threaded iteration over the addresses to migrate. Now, both run in parallel which makes the runtime of the OVM_ETH migration bounded by how quickly we can update the trie.

Batcher Metrics

By removing some code duplication and a more efficient implementation
of the MaxRLPBytes test.

Reusable event metrics modules.

RefMetrics are a reusable metrics module to enable block reference metrics.

The caller of BlockToBatch is sometimes interested in the L1BlockInfo
of the block, so instead of re-extracting it again, we just return it
here.

This is similar to PayloadToBlockRef but takes an interface instead that
e.g. a types.Block fulfills. This way, we can directly extract L2BlockRefs
from type.Blocks that have a valid L1 Info Deposit tx as first tx.

A block could also be converted into an ExecutionPayload, but this would make an
inefficient roundtrip, marshalling and unmarshalling all transactions.

op-proposer: log L2OutputOracle version + address

feat(ctb): Add test for `finalizeBridgeERC721` reverting if the token is not compliant with the `IOptimismMintableERC721` interface

Logs the L2OutputOracle version and address after building
a client to call it. This is generally useful information to
have and future implementations of the `op-proposer` will
need to function differently depending on the version to keep
the software compatible with both permissioned and permissionless
output proposal submission.