refactor(textual): Update Spec to have shorter Any header screen

[amaury1093]

Description

This is a proposal for spec update on Any value renderers to remove the Object: prefix on its header screen. I found out in #13600 that they "object" word came up unnecessarily too often:

{ "text": "This transaction has 1 Message" },
- { "text": "Message (1/1): Object: /cosmos.bank.v1beta1.MsgSend" },
+ { "text": "Message (1/1): /cosmos.bank.v1beta1.MsgSend" },
{ "text": "MsgSend object" },
{ "text": "From address: cosmos1ulav3hsenupswqfkw2y3sup5kgtqwnvqa8eyhs" },
... // indentation omitted

An Any can only pack a protobuf message, so it's always going to be Object. That's why I propose to omit it.

---

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)

[sonarqubecloud]

[Cosmos SDK Core] Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

0.0% Coverage
0.0% Duplication

[amaury1093]

Thanks for the reviews! I would also like someone from the Textual WG to approve this before merging.

[amaury1093]

The only weird output would be this.

The first line will have, in a message context, a field name:

<Field>: /google.protobuf.Any

But the 2nd line will be a naked /Foo. I think it's fine, because nested packed Anys should be extremely rare.

[sonarqubecloud]

[Cosmos SDK] Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

0.0% Coverage
0.0% Duplication

[aaronc]

Why do we still say Foo object after /Foo?

[amaury1093]

We touched on this in yesterday's call, but didn't come to a unanimous conclusion, so here's an issue to discuss more: #14170

[sonarqubecloud]

[Cosmos SDK - Tx] Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information