Cosmos: Circuit Breaker Authorization Issue

A bug was discovered in the Cosmos SDK in which an account that has authorization for some messages in the circuit breaker module could reset the circuit breaker for any message, despite not having that permission. An additional authorization check was added to ensure the permission model is correct. Summary of Impact Circuit Breaker authorization model has a flaw. A user with SOME_MSGs permissions on a single message is able to reset ALL circuit breakers. Details The circuit breaker module is used for turning on or off messages in the Cosmos SDK. The idea is that if a serious vulnerability occurred, an administrator could trip the circuit breaker to disable the message, preventing exploitation. There are two operations that are important for this module: * Trip: Turn off the service. * Reset: Turn on the service after it's been tripped. There are three types of users with this: * ADMIN: Able to trip and reset allcircuit breakers. Additionally, they can grant additional permissions to other users for all user types. * ALL_MSGs: Able to trip and reset all circuit breakers. * SOME_MSGs: Able to trip and reset some circuit breakers. The SOME_MSGs user should only be able to act on particular messages, as designated by the name. This is true for tripping, as you can only trip the allowlisted message. However, this is not true for the reset functionality. If a user is granted permissions to a single message via SOME_MSGs permissions, they are able to reset ALL messages....