Add dubugging of the C++ tests

[NickBettsRandom]

Currently, when the C++ test run they are not running under the debugger (break points are not hit), which makes it hard to find and fix problems. The tests can be run under the debugger by adding the following configuration to the .vscode/launch.json.

    {
      "type": "cppvsdbg",
      "name": "WPILib Test Debug",
      "request": "launch",
      "program": "${workspaceFolder}\\build\\install\\frcUserProgramTest\\windowsx86-64\\debug\\lib\\frcUserProgramTest.exe"
    }

It would be good to have an WPILib: Debug Robot Test command to run them.
Also the existing WPILib: Test Robot Code command does not actually run the tests unless a change has been made to them, which is terribly confusing (and quite odd).
Looking at the extension source this seems like it it should not be too hard, but I'm not familiar with any of the technology being used. If anyone has any hints I may be able to give it a go.

[ThadHouse]

Also the existing WPILib: Test Robot Code command does not actually run the tests unless a change has been made to them, which is terribly confusing (and quite odd).

This is actually caused by gradle itself, and does the same thing in Java as well. It knows it has ran the tests before and passed, and no code changes have happened since, so it determines that the tests don't need to be reran.

As for the rest, the good thing is the gradle support is already there, so it should be pretty easy to just add vscode support. The bigger issue is changing that likely requires changing the vscode library we created, which we haven't updated in 3 years and has to be pushed by one of us. I'll work on doing that this summer.

It used to be possible to do this before 2022, but it was one thing that was lost in the 2022 rewrite.