[TT-1546] add back chain id

[Tofel]

What?

1. add back chainId to Network (if it's not set we will still get it from the RPC node as we do now)
2. allow to initialise ClientBuilder with existing config
3. allow to select active network when building Seth with ClientBuilder

Why?

1. Network names can vary a lot among different applications even for the same network (e.g. Sepolia, Sepolia Testnet, eth-sepolia), which makes it difficult to match Seth network by name. ChainID doesn't have any ambivalence.
2. Some users want to initialise Seth from TOML config and apply some slight modifications to it (e.g. select active network)
3. If you have a Seth config with multiple networks defined, but you don't want to hardcode active network in that config currently you have no easy way of selecting. Thus I've added options to the builder that will allow you to select active networks from all that are present in the config.

---

Below is a summarization created by an LLM (gpt-4-0125-preview). Be mindful of hallucinations and verify accuracy.

Why

The changes improve the flexibility and configurability of the SETH client, notably by introducing a way to specify a configuration path for testing and enhancing the client builder to support modifying an existing configuration or setting a network by chain ID. Additionally, adjustments to gas estimation, error handling, and contract deployment demonstrate a broader effort to refine the tool's usability and reliability for various blockchain development scenarios.

What

• seth/Makefile

  • Added SETH_CONFIG_PATH environment variable to specify a configuration path for testing, enhancing flexibility in test environments.

• seth/README.md

  • Updated documentation to include new client builder methods NewClientBuilderWithConfig and UseNetworkWithChainId, and provided examples of their usage. This improves the documentation's comprehensiveness regarding client configuration.

• seth/client.go

  • Modified to use uint64 for ChainID instead of converting to and from strings, streamlining chain ID handling.
  • Adjusted NewClientRaw to conditionally fetch ChainID if not provided, ensuring the client has the necessary network information.

• seth/client_builder.go

  • Introduced new methods (NewClientBuilderWithConfig, UseNetworkWithName, UseNetworkWithChainId, WithNetworkChainId) for enhanced client configuration capabilities, including support for modifying existing configurations and setting the network by chain ID.
  • Added error accumulation during the build process to provide comprehensive feedback on configuration errors.

• seth/cmd/seth.go

  • Corrected the handling of ChainID to use uint64 directly, aligning with changes in chain ID data types.

• seth/config.go

  • Added ChainID as a uint64 in the Network struct, directly storing the chain ID in its native format for easier access and manipulation.

• seth/config_test.go

  • Added tests for new client builder functionalities, ensuring the behavior aligns with expectations, especially when modifying existing configurations or using new methods to set the network.

These changes collectively enhance the SETH tool's configurability, usability, and reliability, catering to a wider range of blockchain development scenarios.

[cl-sonarqube-production]

Quality Gate passed

Issues
1 New issue
0 Fixed issues
10 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube