Add Amino support for CommunityPoolSpendProposal

[mhagel]

Link to Issue

Closes: #4731

Description of Changes

• Adds Ledger (amino) support for all supported Cosmos onchain transactions except:
  • MsgSubmitProposal with CommunityPoolSpendProposal in v1 (note that this does support it in v1beta1)
  • The automated test for this is skipped and marked for new issue...
• Bumps cosmJs to 0.31.0, and makes associated migration changes

"How We Fixed It"

Added gov/aminomessages.ts to amino registry when creating signingClient

Test Plan

• Note: I (or anybody) can send tokens to whoever wants to QA with a Ledger.
  • Recommended for QA:
    • if running Redis: redis-cli > FLUSHALL (this will clear devnet sandbox params which change with this PR)
    • In Keplr, Settings > General > Manage Non-native Chains > Delete Cosmos Devnet chains (we will re-add them)
• Amino tests added to devnet suite (create both types of proposals, vote).
• CA (click around) tested on local:
  • Using a Ledger device with staked tokens,
  • create Text Proposal and Community Spend Proposal on /csdk-beta, and vote
  • create Text Proposal and vote on /csdk (spend prop for v1 is a follow-up, see below)

Deployment Plan

Other Considerations

• Ledger support for V1 CommunityPoolSpendProposal #4821 for v1 community spend

[mhagel]

Ledger support is ready here for everything except v1 CommunityPoolSpendProposal tx. v1beta1 works, but in v1 I am getting a classic (miselading) Cosmos error from the chain:

Broadcasting transaction failed with code 4 (codespace: sdk). Log: signature verification failed; please verify account number (9799), sequence (2) and chain-id (kyve-1): unauthorized

See https://github.com/hicommonwealth/commonwealth/actions/runs/5883047794/job/15954867599?pr=4811

In the past I have seen this when amino encoding is incorrect, although it is also a general error that pops up if anything is wrong with the TX. Despite the wording of the error, this is probably not a signature error. In manual testing, the message appears correct, so it will take some more investigation to resolve.

I propose that we split off a separate ticket for v1 CommunityPoolSpendProposal ledger support. That will allow the rest of the ledger support to move forward.

[CowMuon]

Great update Mark. Please go ahead and add that new ticket, cross-linking to original ticket for this PR (I know this ain't Jira) and let's get this out of draft.

[mhagel]

Please go ahead and add that new ticket,

@CowMuon New ticket: #4821

let's get this out of draft.

I need to make some updates to our devnet deployments to make this QA-ready. I have tested other chains, but csdk and csdk-beta are not registering unstaked tokens on Keplr. Whoever QAs it would also need a physical ledger device to test with.

@NakulManchanda I believe we may need to get rid of the nginx integration, or adjust it, because it may be affecting RPC requests. Or the problem may be something else. I will get in touch with you for help.

[mhagel]

Latest commit fixes devnet issues. The bootstrap code included is already deployed to the sandboxes and the CI images.

It fixes the native send functionality for keplr. Which means we can test other ledger devices by sending tokens to them.