[Epic] Add Multi-Chain Support for Dry-Run

[nbayindirli]

Previous single-chain impl: https://github.com/hyperlane-xyz/issues/issues/819

• Multi-chain should enable developers to run dry-run against multiple networks at once, likely against multiple anvil nodes

High-level steps

1. Encapsulate sdk's fork.ts util in a class, adding setters to support multiple IPs and Ports
2. Update CLI dry-run logic to use new fork util, support multi-chain selection, and allow developer to dry-run against 1+ networks

[yorhodes]

adding setters to support multiple IPs and Ports

I think a potential simpler solution here can reuse a single anvil process and the anvil_reset, anvil_dumpState, and anvil_loadState

https://book.getfoundry.sh/reference/anvil/#custom-methods

[nbayindirli]

Agreed– so during a dry-run, we will dump & load state multiple times, to and from the same anvil node. This would occur each time we interact with a different network.

Additionally, the dumped state for each forked network can be stored if we want to run future commands against the same augmented fork