feat: Validate Msg proto annotations

[amaury1093]

Description

This PR aims to do 2 things:

• verify that all Msg services have the cosmos.msg.service=true annotation.
• verify that all Msg* messages have the cosmos.msg.signer=... annotation.

If it's not the case, then it prints a warning to StdErr at startup.

It also fixes a couple of wrong proto annotations it caught 💪

Closes: #13405

---

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)

[amaury1093]

This is R4R again

[tac0turtle]

utACK, nice to see it cleaned up some items

[amaury1093]

I had to add this change after #15413.

@aaronc @kocubinski In practice, would we ever want protodesc.Resolver not to be *protoregistry.Files?

[kocubinski]

Maybe for testing failure modes in unit tests?

Edit: If we find a need, we could create an interface in signing like

RangeFiles(f func(protoreflect.FileDescriptor) bool)

and cast to that instead of protoregistry.Files. But since we don't have that need yet, and that would be a non-breaking change, I vote this is fine for now.