Investigate additional security mechanism for module claim mission

[lubtd]

We use right now hooks of modules and the CompleteMission interface to define the logic of claim mission:
Ex: Delegate hook of staking for the staking mission

Nothing prevent right now two modules to register the same mission ID for two different actions. We should explore on an additional mechanism to prevent two modules to register the same mission:
Example, somewhere in app.go

claimKeeper.setMissionAuthorization(
{
  1: staking.ModuleName
  2: gov.ModuleName
}
)