Add support for fork Foundry tests

Related: https://github.com/runtimeverification/evm-semantics/issues/1401

We should consider supporting Foundry fork tests, which would make it easier to reproduce exploits, perform meaningful inter-contract analysis, and simplify the application of FV to the existing test suits that contain fork tests. We can also re-verify the property tests against the updated mainnet state against potentially changing mainnet state (e.g., if other contracts change through a proxy).

The existing workaround is to set the contracts' bytecode using the etch cheatcode (as discussed in https://github.com/runtimeverification/evm-semantics/issues/1401), but that would still require careful reconstruction of the state such as setting storage variables according to their values in a certain block, etc.

Perhaps we might look into re-using the information fetched by Foundry when its run in the fork-test mode:

forge test --fork-url <your_rpc_url>

Start with related issue #1401 and the Foundry fork-testing documentation, then review the existing etch workaround and the forge test --fork-url <your_rpc_url> entry point. Done means defining and validating support for fork tests without manually reconstructing contract state, including tests against the relevant updated chain state.