Use distinct annotations for command-specific properties

[freya022]

Problem

Annotated text commands as well as slash commands suffer from several issues do to all the data being written in a single annotation:

• For multiple commands with the same top-level name, you must specify the same data everytime (like the scope), which causes hard to diagnose issues if the values are not the same everywhere, without even mentioning the maintainability problem
• The description of subcommand groups had a chance to not be applied on the right group
  • This is due to the annotation applying the description to the top-level command, the subcommand group, as well as the subcommand, as all of them share the same description
  • This is also what causes unnecessary application command updates, as the description of subcommand groups would sometimes alternate (partially due an unstable order of reflectively-obtained methods), this did not cause an issue as subcommand groups are not visible on Discord (yet)
• Text commands has a generalDescription property, but this only applies to the text command itself, i.e., not on the text command variation
  • The user may receive a warning if such properties were set more than once on a same command
  • This required a way to sort text command variations, determining which variation would be above every other variation, from which you could take the data

Solution

Properties which are attribuable to only a part of a command (such as the scope which only can be set on the top-level command) will be in a different annotation:

• Slash commands will have 3 annotations:
  • [Required on subcommands] Top-level (scope, defaultLocked, nsfw, description)
  • [Optional] Subcommand group (description)
  • [Required] Slash command (name, group, subcommand, description)
• Text commands will have 2 annotations:
  • [Optional] Text command (path, aliases, description) (path is the path this annotation applies to, if empty, apply on the variation's path)
  • [Required] Variation (path, order, description, usage, example)

Annotations which applies to text commands may appear on a single variation, but they affect the command as a whole, and are not allowed more than once per path

The description for a top-level command can be only be set on either annotations

• Update live templates
• Test built-in help content, see if all descriptions go to the right levels