feat(op-e2e): Deep reorg test

Update

Fix order

wip

wip

Merge Josh's changes + disable parallel runs for `op-e2e` on circleCI

Reduce number of L2 blocks built by decreasing the `SeqWindowSize` + `L1BlockTime`

Submit batch for blocks derived from chain B, verify safe L2 head is accurate

Fixes

Bump to 3 sequence windows

Update

Remove batch submissions on reorged chain

Use `CrossLayerUser` instead of `BasicUser`

Fix

:broom:

de-spaghettify `setupReorgTest`; Correct comments

op-chain-ops: always use magic for transition/genesis block

No longer allow for a configurable L2 genesis/transition
block extradata. The extradata will always be set to
`BEDROCK`. This allows us to have automation to ensure that
the value set as the `L2OutputOracle.startingBlockNumber`
matches the actual L2 genesis/transition block.

Note that the term genesis block and transition block are
used interchangably, the term transition block is used
for upgraded networks.

ci: Fail CI if yarn.lock changes

fix(op-e2e): Include `action` tests in CI

op-chain-ops: export bedrock transition block extradata

Update docker publish target to oplabs-tools-artifacts/images

Makes the extradata for the bedrock transition block
a public variable. This is useful for exporting the
value to be imported in other packages where assertions
can be made to ensure that the extradata is correct.

When fetching the `L2OutputOracle`'s configured starting
block number, the L2 block with that number can be
fetched and then we can assert that it has the magic
extradata.

```bash
$ cast call 0x02Ac1923480E7fd234e7F2Fd11596b9F20372374 'startingBlockNumber()(uint256)'
3855343
```

```bash
$ cast block 3855343 --json | jq -r .extraData
0x424544524f434b
```

Now check like so:

```bash
$ cast --to-ascii 0x424544524f434b
BEDROCK
```

fix: regenerate yarn.lock

contracts-bedrock: check-l2 configurable url

specs: guaranteed gas market cleanup

fix(data transport layer): Fix typescript type resolution

Allows the URL to be configured via CLI params.

- `--rpc-url`

Also optionally accepts a chain id via CLI and asserts
that the remote chain id matches what is passed in via
CLI, only if a value is passed in via CLI.

- `--chain-id`

Can also skip the very long predeploy checking at the
beginning and add in some logs that ensure progress
is happening with `--skip-predeploy-check true`

updates codeowners with round-robin review teams

Running `yarn` causes a diff in the `yarn.lock` file.

fix(ctb): correct usage of legacy in ProxyAdmin

chore(ctb): update semver to 1.0.0

specs: system config unsafe block signer

fix(ctb): minor edit to XDM comment

fix(ctb): comment in SequencerFeeVault

feat(ctb): Forge invariant tests