Remote debugging using sftp/gdbserver (without VS Code Server)

Feature Request

For remote debugging an alternative to deploying VS Code Server would be to use sftp to deploy the cross-compiled executable and gdbserver to debug it.
Especially on a bit more powerful embedded targets this would be great to have. To prevent polluting the system with VS Code files.
And it would allow developers to use their IDE of choice, with the same target image. All that is needed is an sftp server and gdbserver on it.

To get it to work today, Variscite has this documented pretty nice.
Variscite - Yocto Programming with Visual Studio Code

The short version

• Cross-compile the executable on the host system (already possible)
• Deploy the cross-compiled executable using sftp (sftp-server running on the target) - for example use the currently selected CMake target
• Start the gdbserver on the remote system with the just deployed executable

The feature request would be to streamline this approach.

The issue names no implementation files, tests, or entry points. Start by reviewing the existing CMake-target deployment and debugging flow and the linked Variscite workflow; define acceptance criteria for streamlined sftp deployment and gdbserver startup without VS Code Server.