refactor hardhat cct

[aelmanaa]

This pull request significantly refactors the network configuration system for the Hardhat-based CCIP project. The main improvements include consolidating all network configuration data into a single TypeScript source of truth, removing the legacy config.json, and auto-generating types and Hardhat network configs directly from this unified configuration. The documentation and developer workflow are also updated to reflect these changes, making it much easier to add and maintain supported networks.

Network Configuration Refactor and Type Safety Improvements:

• All network configuration data is now defined in a single configData object in config/networks.ts, replacing the previous config.json file and eliminating the need for manual synchronization between multiple sources. [1] [2]
• TypeScript types for networks and EVM chains are now auto-generated from configData, ensuring type safety and reducing maintenance overhead. The Chains and EVMChains types are now derived from the keys and structure of configData. [1] [2]
• Type guards and utility functions (isValidChain, isEVMChain, validateNetworkName) are added to improve type safety and error handling when working with network names throughout the codebase.

Developer Experience and Documentation Updates:

• The README is updated to document the new single-source-of-truth architecture, including clear instructions for adding new networks, required configuration fields, and contract verification steps. The documentation now highlights the use of Etherscan V2 API keys and provides detailed examples for adding new networks. [1] [2] [3]
• The README and code now emphasize that all network-related types and configurations are auto-generated, reducing manual work and potential for errors. [1] [2]

Codebase Cleanup and Task Improvements:

• All references to the old config.json have been removed, and the codebase now imports configuration and types directly from the new config/networks.ts and config/types.ts files. [1] [2] [3] [4]
• Hardhat tasks now use the new validateNetworkName function to ensure only supported networks are used, improving reliability and error messages for developers. [1] [2]

Summary of Most Important Changes:

Network configuration architecture:

• Migrated all network configuration from config.json to a single configData object in config/networks.ts, with auto-generated types for network names and EVM chains. [1] [2] [3]
• Hardhat network configs are now generated directly from configData, ensuring consistency and reducing duplication.

Type safety and developer tooling:

• Introduced type guards (isValidChain, isEVMChain) and a network name validator (validateNetworkName) to enforce correct usage of network names and improve error handling.
• Updated Hardhat tasks to use the new type-safe network name validation. [1] [2]

Documentation and onboarding:

• Refreshed the README to explain the new architecture, provide step-by-step instructions for adding networks, and document usage of Etherscan V2 API keys. [1] [2] [3]

These changes modernize the network configuration workflow, improve maintainability, and make it easier and safer for developers to add and use new networks in the project.

[github-actions]

👋 aelmanaa, thanks for creating this pull request!

To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team.

Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks!