Add support for vesting messages (MsgCreateVestingAccount)

[webmaster128]

There seems to be one message only: https://github.com/cosmos/cosmos-sdk/blob/v0.45.1/x/auth/vesting/types/msgs.go

This came up in #1062 but the author decided to just be selfish and fork away instead of creating a trivial PR to add this type to the codebase.

[dreamcodez]

@webmaster128 this 'selfish' author wanted to test that his approach worked before sending a PR upstream. Also, I have no idea how to get the checked in node_modules build chain working. Please note the number of files changed.

I'm happy to submit these changes upstream when I understand the codebase better and I can clean it up.

[webmaster128]

Hey @dreamcodez, thank you! For CosmJS maintenance we use yarn 3 for package management. This makes the setup a bit tricky. See https://github.com/cosmos/cosmjs/blob/main/HACKING.md for a starting guide how to work in CosmJS. Let me know if something is missing or unclear.

[webmaster128]

@dreamcodez do you want to give this ticket a try? In cosmos/cosmos-multisig-ui#54 you see how the message type is used and the Amino JSON converters are implemented when this is done on the user's side. But it would be great to get it in here to be easily available to every user.

[webmaster128]

In #1114 we have the message type working with sign mode direct.

Unfortunately Amino JSON signing is causing trouble. Looking at cosmos/cosmos-sdk#11019 (review) it seems like the message type was not properly registered in Cosmos SDK 0.44/0.45. However, people report that signing with the Go CLI client and Ledger works, which indicates the same bug we found for authz messages in https://medium.com/p/8754a0dc2a88. Further debugging would be needed which requires getting the raw JSON sign doc during the signing process from the Go CLI.

Is there any value for users to get the direct sign mode merged without Amino JSON support?

[webmaster128]

See #1115 for the follow-up ticket for Amino JSON support