Run the Java Simulate Robot Code command using gradle instead of the debugger extension

[SamCarlberg]

Currently, we use the Java debugger extension and the Red Hat Java extension to launch the simulate command. This has many problems when the robot program uses Epilogue (or probably any other annotation processor where generated class files depend on multiple inputs), due to the eclipse compiler used by the Java extension running incremental compilation; it excludes unchanged files from a compilation unit, which breaks the Epilogue generator that needs full project context. These corrupt files are used for intellisense (which is annoying, but not breaking) and by the debugger extension when it launches the simulator (which is breaking, and badly)

Gradle and the jdk compiler will cause Epilogue to generate correct classes (which also means actual deployed robot programs are correct). Changing the command to run the gradle task and attaching to it as a remote process would avoid the problems created by the incremental compiler.

Related: wpilibsuite/allwpilib#7103, wpilibsuite/2025Beta#20

[SamCarlberg]

Changing build.gradle to include eclipse-specific configurations may also be a fix, without needing to change our extension

redhat-developer/vscode-java#1660 (comment)