ci: Remove legacy labels

contracts-bedrock: delete dead config

op-bindings: make ci faster

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

feat(op-challenger): GetOracleData call in Solver

The only thing that differs is the paths to the contracts

feat(op-challenger): Adds Preimage Data to the TraceProvider

Move the `contracts` directory to `src` and then move
the tests into a top level `test` dir so that its
standard foundry style for a repo.

This is going to break any in flight PRs so worth trying
to get in relatively quickly, will be no fun to rebase a
bunch of PRs.

Will need to follow up with another commit that bumps the
patch versions.

devnet: allow unprotected txs

feat(op-chain-ops): WithdrawalNetwork Type

The `controller` value does nothing as part of
the deployment process. It existed as part of
the upgrade process, no chains will need upgrades
anymore and the modern deploy scripts do not use
it.