Commands V3 is not respected by "Create a new class/command"

[crueter]

With the CommandsV3.json vendordep, Create a new class/command -> Subsystem does not create a Mechanism subclass as would be expected:

[sciencewhiz]

Since they have different paradigms, I don't think it makes sense to have VS Code auto-detect the project and create the appropriate class. For example, i think it would enforce old stereotypes if create Subsystem creates a Subsystem in Commands v2, and a Mechanism in Commands v3.

Back when we had Commands v1 and v2 (or old and new), there were separate templates for each, and the user was responsible for picking the right one. Here's how things were named back when they were separate: https://github.com/wpilibsuite/allwpilib/blob/v2021.1.1/wpilibcExamples/src/main/cpp/commands/commands.json. I created a PR (wpilibsuite/allwpilib#8875) to start down that path by adding (v2) to all the existing templates. I also think it would also be helpful to either filter the list based on what command version the user is using or warn/block from creating the wrong one, but best I can tell that was not done previously.

I think there's also a healthy debate about whether making commands templates for v3 is a good idea, as it pushes people away from idiomatic practices. In my opinion making mechanism template makes sense (but I've heard others who think it's too simple to even be worth it), but I'm not sure it's worth it for commands.

[crueter]

A separate Mechanism template makes sense to me, but I do agree that v3 Command classes don't make much sense.