default launch debug attempts to use unsupported debuggers

### Brief Issue Summary

Cmaketools attempts to launch lldb on linux, something that is explicitely not supported by cpptools.

### CMake Tools Diagnostics

_No response_

### Debug Log

_No response_

### Additional Information

I am using the following kit on a fresh WSL debian machine:
```json
{
"name": "Clang 18.1.3 x86_64-pc-linux-gnu",
"compilers": {
"C": "/usr/bin/clang-18",
"CXX": "/usr/bin/clang++-18"
},
"isTrusted": true
},
```

When launching the default cmaketools debugger target, without manually supplying a launch.json, the following debuggers are tried in the following order:
```
/usr/bin/lldb-mi-18
/home//.vscode-server/extensions/ms-vscode.cpptools-1.19.9-linux-x64/debugAdapters/lldb-mi/bin/lldb-mi
/usr/bin/gdb-18
/usr/bin/lldb-18 # it finds this one, leading to errors..
/usr/bin/gdb
...
```
It should not try to launch lldb debuggers on the linux platform since those are not supported.

Sidenote: Is there a setting to manually override this scanning behavior and instead supply a debugger path yourself, without having to define an entire launch.json file? That would be nice.

Inspect the default debugger-target launch path and its platform-specific debugger selection, then reproduce it with the reported WSL Debian Clang kit. Done means Linux no longer attempts the unsupported lldb debuggers before selecting a supported debugger.

Written by the indexing model from the issue text.