upgrade IBC & lint

[faddat]

Description

Note: this doesn't comply with conventional commits yet, I could squash it to make it do that, though.

• upgrade ibc to v4.4.0
• lint the repository a bit more tightly

Lately I've been interested in making a "platform of chains" and the big blocker is the fact that all of them are a little bit different. The .proto types and interfaces in 47+ have improved a great deal, and that's likely possible now, and usually before bringing the whole thing to 47, I lint the heck out of it to make sure any issues are easier to spot.

Summary:

• upgrade many chains to 47
• make a single front end for may chains, interactive

---

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow-up issues.

I have...

• included the correct type prefix in the PR title
• added ! to the type prefix if API or client breaking change
• targeted the correct branch (see PR Targeting)
• provided a link to the relevant issue or specification
• included the necessary unit and integration tests
• added a changelog entry to CHANGELOG.md
• included comments for documenting Go code
• updated the relevant documentation or specification
• reviewed "Files changed" and left comments if necessary
• confirmed all CI checks have passed

[troian]

hey @faddat, could you split PR into a few atomic pieces.
the very first would be to upgrade ibc-go to v4

[faddat]

yes, absolutely

[github-actions]

Marked as stale; will be closed in five days.

Cut bait or go fishing!