[Bug] Remote debugging not possible

Nobody has claimed this yet.

### Brief Issue Summary

With VS Code, I want to debug my application running on a remote target.

For this, on the target I'm running gdbserver :1234 --attach $(pidof myapp).

I have created a launch.json script for code:

```{
"version": "0.2.0",
"configurations": [
{
"name": "Debug",
"type": "cppdbg",
"request": "launch",
"preLaunchTask": "Debug: Start gdbserver",
"program": "/home/developer/src/build/Debug/myapp_unstripped",
"cwd": "/home/developer/src",
"MIMode": "gdb",
"miDebuggerPath": "aarch64-linux-gnu-gdb",
"miDebuggerServerAddress": "IP:1234",
"stopAtEntry": false,
"logging": {"engineLogging": false},
}
]
}
```

`launch` here is problematic: on stop debugging it will kill my target process.

I can't use "attach": it shows a local PID selector. I tried EVERYTHING. But I still can't understand why something is that hard in 2026 whereas Eclipse has this for decades (at least 2 = 20years). Can anyone please help?

I just want to attach to my remote target, and leave it alone after finish.

### CMake Tools Diagnostics

```shell
No log output.
```

### Debug Log

```shell
No output
```

### Additional Information

_No response_

Start with the launch.json configuration and the CMake Tools debugging path, comparing the existing launch behavior with the attach flow that presents a local PID selector. Done means a remote target can be attached through the CMake Tools workflow and remains running when debugging stops.

Written by the indexing model from the issue text.