QoL -- Chain Opt-in mechanism for bulk attestation node deployment

[kashishshah]

Describe the feature request

If the operator wants to run attestation nodes for multiple chains then they have to repeat some of the deployment steps. We want to improve the user experience and provide a chain opt-in mechanism where the operator can enter the chains that they want to run an attestation node along with some config parameters and the CLI will deploy the nodes for all those chains.

Describe the expected solution

The operators will need to enter the chains for which they want to run the attestation node and provide the config params. All these nodes should be deployed using a single CLI command.

Additional context from @cool-develope 08/13/2024

Seems like we don't need any Smart Contract updates here.

multiple key registering is allowed one signer key per operator Key registering in KMS (even local) is very sensitive and is required the careful operation, I don't think clients are open to bulk operations for that.

Deploying and upgrading nodes, this can be leveraged by bulk operations. To allow it, we are assumming all Smart Contracts staff and KMS configuration are done.

• [x] #116
• [x] #118
• [x] #119

[omarryehia2]

@kashishshah move to v1.5 feature release EPIC. plz confirm

[kashishshah]

@omarryehia2 moved it to v1.5 feature release in the internal release tracker

[cool-develope]

Seems like we don't need any Smart Contract updates here.

• multiple key registering is allowed
• one signer key per operator

Key registering in KMS (even local) is very sensitive and is required the careful operation, I don't think clients are open to bulk operations for that.

Deploying and upgrading nodes, this can be leveraged by bulk operations. To allow it, we are assumming all Smart Contracts staff and KMS configuration are done.

• [ ] Integrate the Signer daemon to simplify the KMS config.
• [ ] Create the universal config file and implement the node operation commands based on it.