Revive IBC Client to Oppy Chain

Summary\n\nThrough accepting this proposal, the expired IBC Tendermint client' 07-tendermint-15' will be revived (or activated) to interconnect the Cosmos SDK blockchains kava_2222-10 (i.e., Kava mainnet) and oppyChain-1 (i.e., Oppy Chain mainnet).\n\n\n## Current Situation\n\nTo be trustworthy, the consensus state of these clients needs to be periodically updated by IBC relayers. However, if the relayers seize their work or the relying chain is terminated, the clients can expire due to their out-of-date consensus state and will be frozen. After being frozen, updating the consensus state of the expired client becomes impossible. As a result, transferring assets through the corresponding channel become impossible and the asset transferred through the channel will be 'frozen' as well.\nIn our case, due to our misconfiguration used to create the client, the client expired and the asset transferred through the corresponding channel was frozen. \n\n\n## Solution\n\nThe ibc-go implementation of the IBC protocol in the Kava Chain exposes a type of governance proposal (i.e., update-client) that enables a community to reactivate an expired/frozen Tendermint client. When such a proposal passes, the state of another (but active and updateable) Tendermint client, which is available on both chains gets copied into the expired client, thus reactivating the expired one. It is to establish this reactivation function that this governance proposal is about.\n\n\n## Governance Votes\n\nYES = The canonical Tendermint client 07-tendermint-15, which interconnects oppyChain-1 (Oppy Chain) and kava_2222-10 will get updated with the state of another active Tendermint client (07-tendermint-49).\nNO = The Tendermint client 07-tendermint-15 remains expired/frozen. This option shows the community's intention that it does not want a functioning IBC connection between Kava Chain and Oppy Chain.\nABSTAIN = You formally decline to vote either for or against the proposal.\n\n\n## Risks:\n\nThere are no significant risks to this proposal being accepted. Passing this proposal can reactivate the connection between KAVA Chain and Oppy Chain and also release 'trapped' Kava on Oppy Chain. Furthermore, reactivating the expired client could bring interoperability and shows the world that Kava is an open, generous, and trustworthy community that welcomes all the chains and projects to join the Kava ecosystem and gives them support when needed.\n\n