[cmd] Deprecate Command.schedule()

[Gold856]

It's a footgun and syntactic sugar over the CommandScheduler's schedule method. We don't need syntactic sugar for a footgun.

[github-actions]

This PR modifies commands. Please open a corresponding PR in Python Commands and include a link to this PR.

[Starlight220]

Usages (such as Trigger) need to be updated

[spacey-sooty]

armbot needs update

[Gold856]

Waiting on #7054 to remove it.

[Daniel1464]

Wait what's the logic over deprecating this again? Scheduling a command in the init block of a class is pretty useful for delayed side effects and such(and having to do CommandScheduler.getInstance().schedule()) is going to be pretty annoying every time this happens

[Gold856]

The purpose is to be annoying. We've seen time after time again that people will use Command.schedule() and be surprised when their commands get cancelled. The intended way to schedule commands is with Triggers, not Command.schedule(). By forcing the CommandScheduler call, the idea is that people will think more about how their schedule call will affect other commands.

[Daniel1464]

Gotchu; i was just thinking that there should possibly be a utility class for launching side effects(such as SideEffects.waitThenRun(0.4, () -> {...}) to replace the command functionality(although im not sure how much people actually use this). That's probably beyond the scope of this pr though

[Starlight220]

Needs a rebase, but looks good.