Ability to run pre-launch health check for new chain integrations

[CharlieMc0]

Is your feature request related to a problem? Please describe.
A pain point we have for new chain integrations if we can’t tell if the OS nodes are prepared until after we enable the new chain and see whether or not txs start to fail. The ability to run a pre-flight check would be great.

**Need to **
Improve the new chain integration process by allowing us to verify OS nodes are setup correctly before a network goes live.

Describe the solution you'd like
We could break this into two phases.

1. Local Check

• An OS operator setups a new RPC in their config file and restarts zetaclientd
• zetaclientd restart checks each entry in the zetaclientd_config.json file and reports the status of each one in logs

2. Network/Decentralized Check

• We ask all OS nodes to setup new RPCs and adjust their configurations
• We add the new chain to chainParams but leave it disabled
• We schedule a pre-launch check at a specific block height that trigger all OS nodes to query their RPC endpoint for a specific Chain ID and writes the results on chain.

Describe alternatives you've considered
The current process of enabling the new chain and then troubleshooting afterwards is challenging and time consuming.
If phase 1 of this is complete, we could do it off-chain will requiring communication with OS node operators. Phase 2 makes it all much easier and helps move us towards an architecture that support full decentralization of OS Nodes.

Motivation and Context
This will make reduce the operational overhead of setting up new chains and helps to further decentralize the OS nodes.

[CharlieMc0]

@gartnera this could tie into your synchronized restart and other zetaclient synchronization efforts.