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

fix(ci): use npm@8.11.0

* bump go-ethereum to 1.12.0 to support finalized and safe block tags

* fix index out of range error for malformed requests

* goimports

Changes the base recordScore to act as if records have been pruned as soon as they are eligible rather than only if the GC has run.

Updates the ci builder Dockerfile to use a pinned version of npm that is
known to not have a module resolution bug found in the default version
of npm that ships with the node version from setup_16.x. Resolves an
issue when importing packages that have hardhat as a dependency, which
causes the current version of npx to try to execute the hardhat binary
found deep within the dependency tree, which in turn causes hardhat to
throw a fit.

op-node: persist p2p bans with expiration time, update ban-expiry gater