refactor: support multiple client chains (Sepolia/Holesky) in configuration

[coderabbitai]

Background

Currently, the configuration in deployedContracts.json uses a generic clientChain key for Sepolia network addresses. With the addition of Holesky network support, we need to refactor this to clearly distinguish between different networks.

Required Changes

1. Rename clientChain key to sepolia in deployedContracts.json for better clarity
2. Update all scripts that reference the clientChain configuration
3. Modify CI workflows to support both networks
4. Add environment variable support to control which network to use during deployment and testing

References

Discussion: //pull/145#discussion_r1943990000

Notes

• This change will require coordination across multiple scripts and CI configurations
• Consider using an environment variable like NETWORK=sepolia|holesky to control which network to use