Debugging mingw application fail if using non-cmd as integrated terminal

### Brief Issue Summary

Debugging MinGW application fails if using non-cmd as an integrated terminal.
I suggest vscode-cmake-tools always use cmd on windows

### Example

For instance I using msys2 as integrated terminal.
```json
"terminal.integrated.profiles.windows": {
"PowerShell": {
"source": "PowerShell",
"icon": "terminal-powershell"
},
"Command Prompt": {
"path": [
"${env:windir}\\Sysnative\\cmd.exe",
"${env:windir}\\System32\\cmd.exe"
],
"args": [],
"icon": "terminal-cmd"
},
"Git Bash": {
"source": "Git Bash"
},
"msys": {
"path": "C:\\msys64\\msys2_shell.cmd",
"args": [
"-defterm",
"-mingw64",
"-no-start",
"-use-full-path",
"-here"
]
}
},
"terminal.integrated.defaultProfile.windows": "msys",
```

When using "msys" as an integrated terminal, the following happens in the terminal but the debugging is not started.


When using "cmd" as an integrated terminal, the following happens and the debugging is started.


Start by reproducing the issue with the provided terminal.integrated.defaultProfile.windows set to msys, then compare the launch behavior with Command Prompt. Trace the Windows debugging entry point and terminal selection logic in the repository; done means MinGW debugging starts with the msys profile while existing cmd behavior remains working.

Written by the indexing model from the issue text.