Add support for optional and params T[] toolshed command arguments.

[ElectroJr]

This PR allows toolshed commands to use optional and params T[] arguments. Optional & variable-length arguments can be truncated using the command terminator ';' or the new explicit pipe symbol '|'. The pipe symbol conflicts with some existing bitwise or commands (|' and |~'), so I just removed the symbolic "name" for those commands. Due to the renaming, this needs a space-wizards/space-station-14/pull/34029 so that the AllCommandsHavePermissions test passes.

I've tried briefly looking around, but didn't find a lot about how to use reflection to check for params collections in .net 9. So I'm not sure how hard it'd be to update or if the current implementation (checking for ParamArrayAttribute) would cause any issues.

This PR also makes varous other toolshed related changes, including:

• The signature of Toolshed type parsers have changed. Instead of taking in an optional command argument name string, they now take in a CommandArgument struct.
• Semicolon terminated command blocks no longer return anything. I.e., i { i 2 ; } is no longer a valid command, as the block has no return value.
  • There's no real reason for this change other than that I think it makes more sense.
• The default auto-completion hint for Toolshed commands have been changed and somewhat standardized. Most type parsers should now have a hint of the form:
  • <name (Type)> for mandatory arguments
  • [name (Type)] for optional arguments
  • [name (Type)]... for variable length arguments (i.e., for params T[])
• The auto-generated output of the help and explain commands have changed to try make the output more readable, and so that they also specify whether a command requires type arguments. E.g., the comp:get command now shows up as comp:get<T>.