Recover frozen IBC client with Cronos (cronosmainnet_25-1)

Original Proposal Text

Juno's IBC light client for Cronos, 07-tendermint-510 (connection-511, transfer/channel-454 Cronos transfer/channel-14), was frozen at Juno height 41334463 (2026-09-01, tx B53498A4D2C07D977154867710C30F76836CE973DB5731EB1FD27C8D35D1BE4B). Cause: Cronos mainnet halted after block 90896189 (2026-08-30 12:38 UTC) and validators performed a coordinated rollback, restarting the chain at 23:49 UTC. While the chain was halted, a relayer whose Cronos node remained on the abandoned pre-rollback blocks updated the client with headers at heights 90897940-90907150. When the canonical header at height 90900000 was later relayed, its timestamp conflicted with those stored states and ibc-go froze the client as misbehaviour. This was a coordinated rollback, not a malicious attack. The relayer setup has been corrected. Safety: no packets were relayed to Juno using the abandoned-block heights (the last receipt on channel-454 is sequence 175, May 2026), and neither side has pending packet commitments. Action: MsgRecoverClient replaces the state of the frozen client with that of substitute client 07-tendermint-592, which tracks canonical Cronos with identical client parameters (trust level 2/3, unbonding 28d, max clock drift 25s). The existing connection and channel are preserved, so all ibc/... denoms on both chains remain unchanged.