Parity between AutoCLI and CLI

[julienrbrt]

Noticed two differences between autocli outputs and previous CLI outputs:

1. JSON and YAML output are nested, while previously not:

current:

$ simd q auth params
max_memo_characters: "256"
sig_verify_cost_ed25519: "590"
sig_verify_cost_secp256k1: "1000"
tx_sig_limit: "7"
tx_size_cost_per_byte: "10"
$ simd q auth params --output json
{"max_memo_characters":"256","tx_sig_limit":"7","tx_size_cost_per_byte":"10","sig_verify_cost_ed25519":"590","sig_verify_cost_secp256k1":"1000"}

autocli:

$ simd q auth params
params:
  max_memo_characters: "256"
  sig_verify_cost_ed25519: "590"
  sig_verify_cost_secp256k1: "1000"
  tx_sig_limit: "7"
  tx_size_cost_per_byte: "10"
$ simd q auth params --output json
{
  "params": {
    "max_memo_characters": "256",
    "tx_sig_limit": "7",
    "tx_size_cost_per_byte": "10",
    "sig_verify_cost_ed25519": "590",
    "sig_verify_cost_secp256k1": "1000"
  }
}

2. Coin display is different (ref: feat(x/distribution): add autocli config query #16218 (review))
   

Proposal

I believe the behavior 1. is better in AutoCLI and should stay coherent with gRPC. We should add an UPGRADING.md disclaimer for that.
Behavior 2. is incorrect and should be fixed.

[julienrbrt]

For point 2, ref: #10863

[julienrbrt]

Closing this as point 2 is tracked by #10863 and point 1 has been solved by a doc update.