[TT-849] Move common test config surface to CTF

[Tofel]

Tried and tested here.

---

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

Why

The changes introduce a new Ethereum network configuration file and a testing configuration file, enhancing the flexibility and capability of defining custom Ethereum networks and test configurations. These changes allow for more precise control over the blockchain environment for testing, including the ability to specify versions, consensus layers, execution layers, and other network-specific parameters.

What

• config/private_ethereum_network.go: Added a new file defining the structure and validation methods for a private Ethereum network configuration, including consensus types, Ethereum versions, execution and consensus layers, and chain configurations. This enables detailed customization of Ethereum test networks.
• config/testconfig.go: Introduced a structure to hold test configuration details, including chainlink image configurations, logging, network settings, and private Ethereum network configuration. This centralizes various test settings for easier management.
• config/tomls/default_ethereum_env.toml: Renamed and relocated the default Ethereum environment TOML file to a more structured directory for configuration files, enhancing organization.
• config/types.go: Added new interface definitions for named configurations and global test configurations, facilitating more flexible and type-safe configuration management across different test environments.
• docker/test_env/*.go: Updated various files in the test environment setup to utilize the new configuration structures, ensuring that Ethereum networks and other test settings can be customized and validated according to the new definitions. This includes updates to how Ethereum versions, consensus layers, and execution layers are handled.
• utils/slice/address.go: Introduced utility functions for validating and deduplicating Ethereum addresses within configurations, improving data integrity and reducing redundancy.

[cl-sonarqube-production]

Quality Gate passed

Issues
0 New issues
3 Fixed issues
3 Accepted issues

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

See analysis details on SonarQube