Investigate status guards for Manual Tournaments

[AlphaKretin]

No description provided.

[AlphaKretin]

How necessary is this? The difference between a tournament being open for registration or not isn't actually a status, and that's the biggest factor I can think of.

[AlphaKretin]

• /channel: Doesn't have much reason to be used after the tournament is IPR, but no harm
• /create: Irrelevant, doesn't act on an existing tournament
• /csv: Only has a point after registration is open, but always useful past that
• /deck: Ditto
• /drop: Ditto
• /finish: Can guard that the tournament is IPR before finishing, but it's also reasonable to allow shutting down a tournament prematurely without starting it for cancellations
• /forcedrop: See /csv
• /host: See /channel
• /info: Always useful
• /list: See /create
• /open: This should actually be restricted to preparing only, I think
• /queue: This could be preparing only, or would just return no results. Also no point prior to opening registration
• /start: See /open
• /timer: See /create
• /update: Changing some settings after the tournament is in progress is a dodgy prospect, but no harm in updating the name or desc...

[AlphaKretin]

In summary, the only commands that I think need status guards are:

• maybe /finish
• maybe /queue
• /open
• /start
• /update on some functionality?

Additionally several commands such as /csv, /deck could benefit from a guard on a registerMessage existing, but that's not a status.