op-e2e: Adjust for updated op-geth API changes

op-chain-ops: Fix data race in error handling

fix log package in proposer/driver

The error channel in the OVM_ETH migration is buffered. In rare cases, errors were written to this channel in such a way that they were not processed by the collector goroutine. This meant that errors were not being caught by the `lastErr != nil` check, and were instead triggering the total supply check below.

This error reliably reproduces when running the new TestMigrateBalancesRandomMissing test. This test generates a random state, and randomly removes an address/allowance from the witness data. It runs this 100 times per test. We didn't catch this with the other random test because it doesn't exercise the error handling codepath.

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.