WPILib: Debug will result in a non-booting robot program until a regular deploy

[daltzctr]

Reproduction:

1. Debug a Java program "WPILib: Debug a Robot Program"
2. Reboot the Systemcore
3. The FIRST Driver Station always results as "No code"

This is likely due to the debug command replacing robotCommand.args with the debug server start, which requires an incoming debug connection before allowing to continue. The roboRIO solved this by having a separate robotCommandDebug script that was manually executed for debug, but boot would always use the regular robotCommand script.