feat: upgrade ibc-go from v2 to v4.3.0 (with cosmos-sdk v0.45.12)

[youngjoon-lee]

Motivation

Susannah, [Feb 2, 2023 22:12:17]: Hello, I have queried medibloc and see that you are using v2.0.3 of ibc-go which is in the end of life. This means that patches and bug fixes are no longer back-ported to this version. We strongly encourage you to upgrade your version of ibc to v4.2.0, this is because v3.4.x will be in end of life in the middle of march. The migration documentation to go from v2 to v3 is here https://ibc.cosmos.network/main/migrations/v2-to-v3.html and for v3 to v4, take a look here https://ibc.cosmos.network/main/migrations/v3-to-v4.html

What I did

• Upgraded ibc-go from v2 to v4
  • Without adopting the following new features:
    • ICS27 Interchain Accounts (aka, ICA)
    • ICS29 Fee Middleware. For more details, see a comment below.
  • This requires us to upgrade wasmd to v0.30.0+ and cosmos-sdk to v0.45.12+. For more details, please see a comment below.
  • There are a lot of changes in app.go. I put reference links as PR comments below.

Tests

• Tested IBC transfers manually with a Panacea Localnet and the Osmosis Mainnet.
  • Panacea -> Osmosis: Success
  • Osmosis -> Panacea: Success
• Also tested IBC transfers before and after upgrading the chain from v2.0.5 to HEAD.

Future work

• Automate IBC tests by referring to e2e tests in ibc-go, gaia, or osmosis.