fix(ctb): Slither Triaging and Docs

contracts-bedrock: fail on warnings

op-upgrade: extended pause

feat: Pin Slither Analyzer Version

contracts-bedrock: Update protocol versions in config to match deployed

contracts-bedrock: add Kontrol CI setup

ctb: Fix argument ordering on oracle assertions

feat(op-challenger): Game Player Prestate Validation

Updating to fix most shellcheck findings. Kontrol commands do not run properly when the variable is quoted

Updating to fix most shellcheck findings. Kontrol commands do not run properly when the variable is quoted

build(deps-dev): bump vite from 5.0.5 to 5.0.6

contracts-bedrock: fix base sepolia config

contracts-bedrock: flexible deploy script addresses

contracts-bedrock: update pgn sepolia deploy config

See explanation in https://github.com/ethereum-optimism/optimism/pull/8515

Related to:
- https://github.com/ethereum-optimism/optimism/pull/8519
- https://github.com/ethereum-optimism/optimism/pull/8520

Value sourced from:
https://sepolia.etherscan.io/address/0x2615B481Bd3E5A1C0C7Ca3Da1bdc663E8615Ade9#readProxyContract

Address sourced from:
https://github.com/ethereum-optimism/superchain-registry/blob/fb3433d89a72df5809255c065b4783fa393608d8/superchain/extra/addresses/sepolia/zora.json#L6C27-L6C69

devnet: Convert devnet-allocs to Anvil

See https://github.com/ethereum-optimism/optimism/pull/8515 for
explanation. Also related to https://github.com/ethereum-optimism/optimism/pull/8519.

Value fetched from:
https://sepolia.etherscan.io/address/0xD5bAc3152ffC25318F848B3DD5dA6C85171BaEEe#readProxyContract

Address sourced from:
https://github.com/ethereum-optimism/superchain-registry/blob/fb3433d89a72df5809255c065b4783fa393608d8/superchain/extra/addresses/sepolia/pgn.json#L6C27-L6C69

See https://github.com/ethereum-optimism/optimism/pull/8515 for
explanation. Also related to https://github.com/ethereum-optimism/optimism/pull/8519.

Value fetched from:
https://sepolia.etherscan.io/address/0xD5bAc3152ffC25318F848B3DD5dA6C85171BaEEe#readProxyContract

Address sourced from:
https://github.com/ethereum-optimism/superchain-registry/blob/fb3433d89a72df5809255c065b4783fa393608d8/superchain/extra/addresses/sepolia/pgn.json#L6C27-L6C69

Makes the L1 starting blocknumber concrete.
See commit message in https://github.com/ethereum-optimism/optimism/pull/8515
for an explanation.

The value in the config comes from here:
https://sepolia.etherscan.io/address/0x84457ca9D0163FbC4bbfe4Dfbb20ba46e48DF254#readProxyContract

The contract address sourced from here:
https://github.com/base-org/contract-deployments/blob/910151eb2eed3542efbb4ccf7e38d1ed3b79d8f5/sepolia/2023-09-26-deploy/deployed/addresses.json#L10C27-L10C69

Makes the L1 starting blocknumber concrete.
See commit message in https://github.com/ethereum-optimism/optimism/pull/8515
for an explanation.

The value in the config comes from here:
https://sepolia.etherscan.io/address/0x84457ca9D0163FbC4bbfe4Dfbb20ba46e48DF254#readProxyContract

The contract address sourced from here:
https://github.com/base-org/contract-deployments/blob/910151eb2eed3542efbb4ccf7e38d1ed3b79d8f5/sepolia/2023-09-26-deploy/deployed/addresses.json#L10C27-L10C69

Updates the `l2OutputOracleStartingTimestamp` to a concrete value
rather than using `-1` which symbolizes "grab the latest L1 timestamp".
We often want to simplify the initial deployment but then do not want to
overwrite the value in storage when generating an upgrade transaction.
Right now `op-upgrade` uses the values in these config files. The code
enforces that it is not -1 to ensure that we do not write over the
value. The value really should be exactly the same. The state diff
tooling will be able to make assertions on this in the `superchain-ops`
post hook.

This commit simply updates the starting timestamp to the exact value
that was set on sepolia. The etherscan link can be found here:
https://sepolia.etherscan.io/address/0x90E9c4f8a994a250F6aEfd61CAFb4F2e895D458F#readProxyContract

The new storage setter contract with ability to set multiple
slots in a single call is deployed at [0xd81f43eDBCAcb4c29a9bA38a13Ee5d79278270cC](https://etherscan.io/address/0xd81f43edbcacb4c29a9ba38a13ee5d79278270cc#code).
It was deployed with create2 and should also be on goerli + sepolia and
ay other chain that has a superchain deployed on it.

Manual calls to `upgradeAndCall` are made. There isn't a great way to
support multiple upgrades at a time within `op-upgrade` so adopting a
"release" model where `op-upgrade` supports building a single version to
another single version makes the most sense. It is too difficult given
the current abstractions to build something that supports any upgrade to
any upgrade arbitrarily. This sort of system is certainly possible to
build but we would need to think more about the abstractions.

One thing is this does not support a reverse upgrade aka downgrade.

Each storage slot that was set as part of the upgrade to MCP is removed
using the `StorageSetter` contract. A link to the storage layout file
is included for each call to `setStorage`.