Set the chain id to be a number that has not been used yet.
Update the batch inbox address so that it corresponds to the
chain id. Also update the gov token owner to be the eoa
that is the final system owner.

Adds the deploy config for sepolia. Also clean up a little
bit of dead code and parse sepolia L1 and L2 in the deployer
script. Optimistic Kovan had a chain id of 69 and is now deprecated,
so re-using 69 for Optimistic Sepolia so that 420 can be used
by goerli still while both goerli and sepolia run in parallel.

To review the deploy config, the values should all match goerli
except for the eip 1559 params which should now match mainnet.
The chainids should also be different.

Merge pull request #6503 from ethereum-optimism/dependabot/go_modules/github.com/mattn/go-isatty-0.0.19

build(deps): bump github.com/mattn/go-isatty from 0.0.17 to 0.0.19

Merge pull request #6505 from ethereum-optimism/dependabot/go_modules/github.com/multiformats/go-multiaddr-0.10.1

build(deps): bump github.com/multiformats/go-multiaddr from 0.8.0 to 0.10.1

After merging https://github.com/ethereum-optimism/optimism/commit/2901c666d25b2250f51394445ae72ca7b3f31daf
which deleted the labeler config, CI now errors. This deletes the CI job
responsible for labeling, since its config is gone now.

build(deps): bump golang.org/x/time from 0.0.0-20220922220347-f3bd1da661af to 0.3.0

Bumps [golang.org/x/time](https://github.com/golang/time) from 0.0.0-20220922220347-f3bd1da661af to 0.3.0.
- [Commits](https://github.com/golang/time/commits/v0.3.0)

---
updated-dependencies:
- dependency-name: golang.org/x/time
  dependency-type: direct:production
  update-type: version-update:semver-minor
...
Signed-off-by: dependabot[bot] <support@github.com>

Bumps [github.com/multiformats/go-multiaddr](https://github.com/multiformats/go-multiaddr) from 0.8.0 to 0.10.1.
- [Release notes](https://github.com/multiformats/go-multiaddr/releases)
- [Commits](https://github.com/multiformats/go-multiaddr/compare/v0.8.0...v0.10.1)

---
updated-dependencies:
- dependency-name: github.com/multiformats/go-multiaddr
  dependency-type: direct:production
  update-type: version-update:semver-minor
...
Signed-off-by: dependabot[bot] <support@github.com>

Bumps [github.com/mattn/go-isatty](https://github.com/mattn/go-isatty) from 0.0.17 to 0.0.19.
- [Commits](https://github.com/mattn/go-isatty/compare/v0.0.17...v0.0.19)

---
updated-dependencies:
- dependency-name: github.com/mattn/go-isatty
  dependency-type: direct:production
  update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <support@github.com>

monorepo: add dependabot support

ci: Remove legacy labels

contracts-bedrock: delete dead config

op-bindings: make ci faster

Adds a dependabot.yml file from https://github.com/celestiaorg/optimism/blob/celestia-develop/.github/dependabot.yml

Based on conversation in https://github.com/ethereum-optimism/optimism/issues/5764Co-authored-by: refcell.eth <abigger87@gmail.com>
Co-authored-by: <mjsevey@gmail.com>

op-challenger: Execute cannon

The last line emitted by programs typically doesn't include a newline.

In the past, we used the `SR-Risk` and `C-Protocol-Critical` labels to require specific engineers to review PRs touching sensitive code:

- `SR-Risk` would tag @maurelian whenever legacy mainnet smart contracts were touched.
- `C-Protocol-Critical` would tag @tynes or @smartcontracts whenever smart contracts or `l2geth` were touched.

Since launching Bedrock, the `SR-Risk` label was removed from the `labeler` workflow, so it was never being applied. `C-Protocol-Critical` was still being applied, however it had no effect apart from blocking Mergify and pinging Mark/Kelvin unnecessarily since it is `CODEOWNERS` and not the label that prevents merge.

Given that we've started using `CODEOWNERS` and the fact that the labels were broken, this PR removes these legacy labels altogether.

Net yet providing the local game data to pre-image oracle server.

contracts-bedrock: foundry-ify

op-challenger: Pass a context through to TraceProvider

op-bindings should no longer depend on JS packages
for CI to run, this will make it much faster.

feat(proxyd): sender rate limiter should check chain id

Will enable trace generation processes to terminate cleanly when op-challenger is shut down.

op-challenger: Add cannon-server and cannon-snapshot-freq flag