Migrate remaining CLI cmd's to proto

[anilcse]

A few cli commands are still using amino or couldn't be easily migrated to use the proto pathway. These were discovered and flagged in #6859. Migrate them to use proto.

• x/auth Migrate {x/auth, x/gov, x/staking} missing CLI queries to proto #6994
• x/gov Migrate {x/auth, x/gov, x/staking} missing CLI queries to proto #6994
• x/distribution
  • GetCmdSubmitProposal -> ParseCommunityPoolSpendProposalJSON Migrate missing x/distribution CLI queries to proto #7244
  • NewWithdrawAllRewardsCmd Migrate missing x/distribution CLI queries to proto #7244
• x/staking Migrate {x/auth, x/gov, x/staking} missing CLI queries to proto #6994
• x/ibc (things have been migrated to proto but arrays of interfaces are being printed and jsonpb doesn't know what to do with that. They probably need to be wrapped in Any) /cc @fedekunze
• Remove client.Context.PrintOutputLegacy (from Require proto.Message in client.Context.PrintOutput #6999)

[fedekunze]

@anilcse @aaronc can you paste an example blob of how the output for the IBC queries looks like? We can tackle it this week

[aaronc]

I don't have IBC test data to do that @fedekunze. Once #6999 is done, you just need to try to use PrintOutput instead of PrintOutputLegacy and you'll see the errors.

[sahith-narahari]

@alexanderbez QueryTxsByEvents uses TxSearch from tendermint which uses slightly different pagination. This causes some inconsistency in queries using this.

cosmos-sdk/x/auth/client/query.go

Line 46 in 20c80cf

resTxs, err := node.TxSearch(query, true, page, limit, orderBy)

One option I can think of is fetch all data, and paginate in sdk to act similar to other queries. Any thoughs?
cc @aaronc @anilcse

[alexanderbez]

I would honestly opt to use Tendermint's pagination when it comes to tx searching. I don't think getting all txs behind the scenes is a good strategy.

[clevinson]

@anilcse can you provide a written update for this issue here?