There was previously a concept in the deploy script that
would check a `.chainId` file on disk against the remote chainid.
This check became problematic because of the parallel nature of
foundry tests that caused it to attempt to read/write the same
file to disk many times in parallel and then it caused a lot
of flakes around the file not existing. Remove this feature
from the deploy script to reduce the complexity of it. We need
less complexity and rely on instead simulations and assertions
for correctness. The assertions can expect a particular chainid
instead of using the local filesystem. This also ties into
the migration of the deployment artifacts away from being in
`contracts-bedrock` and instead towards the superchain registry.