fix: Incorrect amino names provided in RegisterConcrete

[poorphd]

Description

• The amino.name tags in .proto files do not match the names used in RegisterConcrete calls.
• These discrepancies could lead to issues with JSON serialization/deserialization.
• This patch is ensuring consistency between .proto tags and RegisterConcrete calls is crucial for correct behavior.
• amino names follow canto/x/{module_name}/{msg name} convention except govshttle (too long to be registered with amino)

Closes: https://github.com/code-423n4/2024-05-canto-findings/issues/2

---

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...

• [x] targeted the correct branch (see PR Targeting)
• [ ] provided a link to the relevant issue or specification
• [ ] included the necessary unit and integration tests
• [x] reviewed "Files changed" and left comments if necessary

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 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)

[dudong2]

If the amino name is longer than 40 characters, there will be problems signing the ledger. For this reason, even in the cosmos-sdk, most msgs are registered in the form of cosmos-sdk/Msg..., except for those that need to be added in common for multiple modules, such as MsgUpdateParams. I think aligning with this convention is the right way to go, so I don't think this pr should be applied.

ref. https://github.com/cosmos/cosmos-sdk/issues/10870