The address was not being referenced resulting in a bug. We should
delete this task eventually and have coverage of this with op-e2e
although this does cover the hardhat deployments which op-e2e does
not cover. Perhaps this should live in hive then longer term.
Ported from the `feat/mainnet` branch.

contracts-bedrock: mainnet-deployment

refactor(proxyd): order params chronologically: latest, safe, finalized + small fixes

Deploy the contracts to be used for the mainnet deployment

contracts-bedrock: mainnet-deployment

feat(op-challenger): Challenger types and enum string refactor

These values must be updated day of

contracts-bedrock: mainnet proxy admin owner config

feat(proxyd): track consensus for {safe,finalized} blocks and rewrite tags

Sets the proxy admin owner to the gnosis safe on L2.
I double checked that `proxyAdminOwner` is the appropriate config
value, as you can see
[here](https://github.com/ethereum-optimism/optimism/blob/06245265f0c741c2f316d40052115ebcefeeb6e3/op-chain-ops/genesis/config.go#L471).
There is a different config value for the L1 that is the
`finalSystemOwner` as seen [here](https://github.com/ethereum-optimism/optimism/blob/06245265f0c741c2f316d40052115ebcefeeb6e3/packages/contracts-bedrock/deploy/021-SystemDictatorSteps-2.ts#L311)
and
[here](https://github.com/ethereum-optimism/optimism/blob/06245265f0c741c2f316d40052115ebcefeeb6e3/packages/contracts-bedrock/contracts/deployment/SystemDictator.sol#L436).
as well as
[here](https://github.com/ethereum-optimism/optimism/blob/06245265f0c741c2f316d40052115ebcefeeb6e3/packages/contracts-bedrock/deploy/019-SystemDictatorInit.ts#L47).

External links:
- https://app.safe.global/home?safe=oeth:0x7871d1187A97cbbE40710aC119AA3d412944e4Fe
- https://optimistic.etherscan.io/address/0x7871d1187A97cbbE40710aC119AA3d412944e4Fe

op-node: Remove peer scores once the retain period is reached

op-e2e: pending block test + op-geth update

feat: Add docker-compose to indexer