feat(networkconfig): CLI for custom SSV config generation

[nkryuchkov]

Part of PRs that will replace #1308

Based on #2153

[codecov]

Codecov Report

Attention: Patch coverage is 24.19355% with 94 lines in your changes missing coverage. Please review.

Project coverage is 49.5%. Comparing base (ae9dde4) to head (ff3f2d2).
Report is 1 commits behind head on networkconfig-from-beacon-node.

Files with missing lines	Patch %	Lines
cli/generate_config.go	0.0%	64 Missing ⚠️
cli/operator/node.go	0.0%	18 Missing ⚠️
networkconfig/ssv.go	71.4%	8 Missing and 4 partials ⚠️

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[iurii-ssv]

Minor suggestions

[iurii-ssv]

Since we are manually mapping SSVConfig <-> marshaledConfig fields it's probably a good idea to add a test that would check:

• unmarshal->marshal (both yaml and json representations) yields the same result
• and also to make sure newly added field is converted (and not missing) we maybe could hash string-representation of sample config and compare hash directly (so that if new field is added the actual hashed value would become different and we'll be notified by test failing)

although I guess that wouldn't work if the order of fields isn't preserved/sorted ... maybe we could enable sorting if that makes sense ?

I haven't checked for Yaml but looks like JSON marshaling applies sorting (from func description):

// Map values encode as JSON objects. The map's key type must either be a
// string, an integer type, or implement [encoding.TextMarshaler]. The map keys
// are sorted and used as JSON object keys by applying the following rules,
// subject to the UTF-8 coercion described for string values above:
//   - keys of any string type are used directly
//   - keys that implement [encoding.TextMarshaler] are marshaled
//   - integer keys are converted to strings

[Copilot]

Pull Request Overview

This PR implements a CLI tool for generating custom SSV node configuration files and updates the network configurations by converting registry contract addresses from strings to ethcommon.Address. Key changes include:

• Updating the Options struct in operator/node.go with a new CustomNetwork field and deprecating CustomDomainType.
• Converting registry contract address fields from string to ethcommon.Address across various network configuration files.
• Adding a new CLI command (generate-config) and corresponding documentation for streamlined configuration generation.

Reviewed Changes

Copilot reviewed 14 out of 14 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
operator/node.go	Introduces CustomNetwork field and deprecates CustomDomainType with updated comments.
networkconfig/test-network.go	Converts registry contract address to ethcommon.HexToAddress.
networkconfig/ssv.go	Changes RegistryContractAddr to ethcommon.Address and updates JSON/YAML marshaling.
networkconfig/sepolia.go	Uses ethcommon.HexToAddress for registry contract address conversion.
networkconfig/mainnet.go	Uses ethcommon.HexToAddress for registry contract address conversion.
networkconfig/local-testnet.go	Uses ethcommon.HexToAddress for registry contract address conversion.
networkconfig/hoodi.go	Uses ethcommon.HexToAddress for registry contract address conversion.
networkconfig/hoodi-stage.go	Uses ethcommon.HexToAddress for registry contract address conversion.
networkconfig/holesky.go	Uses ethcommon.HexToAddress for registry contract address conversion.
networkconfig/holesky-stage.go	Uses ethcommon.HexToAddress for registry contract address conversion.
networkconfig/holesky-e2e.go	Uses ethcommon.HexToAddress for registry contract address conversion.
cli/operator/node.go	Updates usage of the registry contract address and logs a warning for deprecated usage.
cli/generate_config.go	Adds a new CLI command that generates a configuration file based on passed flags.
cli/GENERATE_CONFIG.md	Provides documentation on using the new configuration generator command.