fix(droid-control): support tctl on Windows

[factory-davidgu]

Description

On Windows, tctl passed its generated .sh runner directly to Tuistory. Windows followed the shell script file association and opened Git Bash/Mintty outside Tuistory's PTY, leaving Droid Control with blank output and orphaned terminal windows.

Windows MSYS environments now launch the generated runner explicitly through bash.exe. Both executable paths use DOS short paths because Tuistory's Windows command parser does not preserve quoted executable paths containing spaces. Linux and macOS behavior is unchanged.

Potential Risk & Impact

• The new path only runs under MINGW, MSYS, and Cygwin.
• Windows execution now requires cygpath, which ships with the Git Bash environment already required to run tctl.
• Tuistory recording uses the same explicit Bash runner path.

How Has This Been Tested?

• bash -n plugins/droid-control/bin/tctl
• Windows non-interactive smoke test through the cloned tctl: captured TCTL_ECHO_OK
• Windows interactive smoke test through the cloned tctl: typed a PowerShell command and captured TCTL_INTERACTIVE_OK
• Confirmed the fixed wrapper no longer leaves test-related Git Bash, Mintty, shell, or Bun processes running

[factory-ain3sh]

nice!