Recover expired IBC client 07-tendermint-45 (Osmosis), second attempt

Original Proposal Text

Recovers the expired IBC client 07-tendermint-45 (Chihuahua's light client of osmosis-1, used by channel-7 Osmosis channel-113) with the active substitute 07-tendermint-226. Proposal 98 asked the same and passed, but its execution failed ("subject client state does not match substitute client state"): the substitute 07-tendermint-224 was created with a relayer's defaults, max_clock_drift 600s, while 07-tendermint-45 has 25s. MsgRecoverClient requires every parameter to match except height, trusting period and chain id. 07-tendermint-226 is a clone of 07-tendermint-45: identical client state, only the latest height moved to a recent osmosis-1 header (agreed by several independent RPCs) and a 9-day trusting period. It was checked against the ibc-go v8.7.0 rules, and the whole recovery was rehearsed on a fork of mainnet state: a 600s substitute fails with the same error as proposal 98, the clone passes, 07-tendermint-45 becomes Active and accepts new Osmosis headers. After recovery a relayer refreshes the client daily so it cannot expire again.