Prop 422: Update IBC Client for Cerberus - 2nd time

The Cerberus chain spent 1.5 weeks in halt due to the upcoming Dragonberry patch. Due to this halt, the IBC channel is currently in a frozen state.
The 8th November, a new client and channel was created in order to attempt revival of the IBC channel. After client creation, a proposal was created in Osmosis ( proposal 357 ), but the counterpart proposal in Cerberus failed to be submitted (reason: software bug has been corrected in upgrade v3.1.0)(lesson learnt: try the little chain beforehand)

# Commonwealth discussion :
Check out the Updated discussion as well as the previous discussion .

# Upgraded cerberus proposal counterpart:
Proposal 30 is up for voting . This has been possible only due to the software upgrades.

# Stuck ibc funds:
If this proposal passes together with the counterpart proposal, it is expected that the client is updated and the stuck assets in IBC can be transfered again.

# Halt timing:
The dragonberry security issue was addressed by halting the chain and implementing further versions of the Cosmos SDK in Cerberus Testnet. Due to an expected further halt on the testnet, the halt timing was extended more than a week.

# Risk due to low liquidity:
The liquidity pool of Cerberus is very small. Backed by only 8000USD equivalent in Osmo at the time of submitting the proposal.
This pool can experience high volatility due to the users cashing out, validators exiting the chain (the chain lost 35 validators since October) or the founder abandoning the project. IBC communication has been interrupted for 4 months.
# Parallel events:
The closure of the chain is being discussed and will be voted via governance. The creation of a new chain from scratch for the remaining community is being discussed;