✨(gentest): Add support for chain_id

[raxhvl]

Would be nice to extend the interface to allow specification of other chains (especially testnets - we could test with sepolia, for example).

Also, modify the docstring to have a pythonic one-liner with an abbreviated tx.hash and chainid. The full tx.hash can be then provided below with link.

[danceratopz]

It's worth taking a look at foundry's cast CLI, at least for inspiration regarding cli design.

I would love to be able to use it within EEST, but we've tried hard to remove non-python dependencies to make it easy for new test developers getting started. If you feel it would add a lot of value, we can reconsider.

[raxhvl]

I completely agree with you. Let's spec out an awesome interface.

[raxhvl]

Here are two ways to implement this.

A) Add chain ID

uvx gentest --chainid 1 ...

We could add a chain id to the env.yaml

remote_nodes:
  - name: mainnet
    node_url: <>
+  chainid: 1

This approach requires verifying the chainid using RPC before running tests to ensure a match. Otherwise, the setup below will work, but ideally, it shouldn’t.

uvx gentest --chainid 365 ...

remote_nodes:
  - name: mainnet
    node_url: <>
+  chainid: 365

B) Select using network name (preferred)

If the goal is to simply select one of many available remote nodes then we can take a simpler approach.

Remote nodes could be renamed to network (friendly name for rpc node used elsewhere) in env.yaml.

Then we could use

uvx gentest  --network mainnet ...

networks:
  - name: mainnet
    node_url: <>
    
  - name: sepolia
    node_url: <>

If no network is selected, it will use the first network as default