feat(textual): Add client-side infra

[amaury1093]

Description

Closes: #13747

• Add clientCtx support and CLI flags for Textual (will throw an error for now if used)
• Add keyring support for Ledger devices
  • To tell the device whether the bytes we're sending are TEXTUAL bytes or AMINO_JSON bytes, we pass a byte flag called P2, which can be 0 or 1. To achieve this, I needed to break some keyring APIs for this new argument, as well as add a new LedgerPrivKeyAminoJSON interface so that ledger priv keys have 2 Sign methods.
  • Let me know if you can think of better ways to achieve this.
• Add ante handler tests to make sure Textual passes sig verification.

Manual Testing

I managed to sign on my Nano S by performing the following changes on this PR (see as diff):

• Install the new Cosmos app >=v2.35.1 of https://github.com/cosmos/ledger-cosmos
• remove these lines which are CLI guards which prevent Textual
• enable SIGN_MODE_TEXTUAL in DefaultSignModes
• Add these two lines on top of simapp/app_v2.go (won't be necessary after Add support to plug gogo's registry into Textual #14647)

	_ "cosmossdk.io/api/cosmos/bank/v1beta1"
	_ "cosmossdk.io/api/cosmos/crypto/secp256k1"

---

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
• followed the guidelines for building modules
• 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

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

• confirmed the correct type prefix in the PR title
• confirmed ! in the type prefix if API or client breaking change
• confirmed all author checklist items have been addressed
• reviewed state machine logic
• reviewed API design and naming
• reviewed documentation is accurate
• reviewed tests and test coverage
• manually tested (if applicable)

[julienrbrt]

Somewhat unrelated could you make proto-gen, the changes are related to textual.

[julienrbrt]

utACK.

[julienrbrt]

It is a bit confusing I think given that they both do the same thing. Except one with a bank keeper and the other using gRPC. Especially since one constructor lives in client and the other on in auth/tx.
If they were in the same file that would be easier to compare and see they do the same thing.