Changes to Command keys and Name

[robhruska]

This contains breaking changes, but is only a minor version update.

• Lifted a bunch of unnecessary restrictions on Command key values.
• Command constructors now take strings instead of GroupKeys since there isn't any validation that needs to happen on the keys.
• Command constructors require a new group key (first argument) that's used to help group and name the Command. We were previously using the Assembly name for this, which was unpredictable.
  • Group keys will often be the "owner" of the command, i.e. the squad that maintains the code. Examples: recruit-client, recruit-internal, monolith-client-athlete, monolith-client-team.
  • Some commands (e.g. mongo/sql wrappers) may have groups like common, common-mongo, or platform.
  • These changes mean Command names will now look like recruit-client.GetRecruitTeam and monolith-client-athlete.GetAthletes.
  • Group keys that contain . (dot) characters will have them converted to dashes to maintain a "two-level" namespaced Name.
• Command Names are cached internally to avoid rebuilding them for every Command instance.

Deployment Considerations

• This needs to go into hudl and hudl-recruit at the same time. We'll want to rebuild the hudl-recruit DLLs and copy them into hudl to get the updated recruit commands.