🔧 Evaluate batching compatibilities with Horocrux and consensus key rotation

[hacheigriega]

🔧 Chore

The SEDA Signer setup is associated with CometBFT's priv_validator_key.json in multiple ways:

• The signer takes the file path to the validator key file so that it can save the SEDA key file in the same directory.
• Following refactor(abci): Batch signing and signature verification refactor #413, the signer now reads the validator key file during setup to determine the node’s consensus address. However, we have not yet accounted for scenarios involving validator consensus key rotation. (see https://github.com/cosmos/cosmos-sdk/blob/036183e93bec2bdce4b98949e051d433dfc9f1a3/docs/architecture/adr-016-validator-consensus-key-rotation.md)

This issue also calls for examining the signer's compatibility with the Horocrux signing service. (see https://github.com/strangelove-ventures/horcrux/blob/main/docs/migrating.md)