This change updates the e2e Setup logic and all other parts of the runner that use its code to accept list of IP addresses from already existing infrastructure to be used when generating the testnet configuration.

The change adds two new flags

1. --infrastructure-type: The type of the backing infrastructure, either 'digital-ocean' or docker
2. --infrastructure-data: The path to a file containing information on already existing infrastructure.

This new infrastructure-data flag selects the path to a json file whose contents can be deserialized into the new InfrastructureData type. This type contains a map of node name to IP address. The map is then used when constructing the testnet. Instead of generating a new IP address for each Tendermint node, the code reaches into the map to determine what the IP address is. A docker variant of this is also defined that, instead of reading data from disk, generates a new set of IP addresses per the already existing logic for IP generation.

This change also adds a new infra.Provider interface type. The Provider currently only has one method, Setup that sets up any configuration files for the specific infrastructure being used. For docker, this method generates the docker-compose.yaml file. For digital-ocean, the method is a Noop. This type borrows from the TestnetInfra type created for the runner in the now defunct v0.36.x code as part of #8754. The hope would be to gradually add more functionality to the infra.Provider until it is much closer to what is implemented previously.

Closes: #9587

PR checklist

• Tests written/updated, or no tests needed
• CHANGELOG_PENDING.md updated, or no changelog entry needed
• Updated relevant documentation (docs/) and code comments, or no
  documentation updates needed