Does this issue occur when all extensions are disabled?: Yes/No

• VS Code Version: 1.65.2
• OS Version: Windows_NT x64 10.0.18363

Steps to Reproduce:

1. Create empty directory with an extension subdirectory
2. Add workspace with two folder paths - . and ./extension/
3. Put the official VSCode Extension webview sample in the extension subdirectory https://github.com/microsoft/vscode-extension-samples/tree/0d36653/webview-sample
4. cd extension && npm ci
5. Open the workspace in VSCode
6. Press F5 to start debugging
7. ! Debugging spins, but never starts (new VSCode window never opens).

Why?
9. extension/tasks.json customizes npm watch to be a background task: "isBackground": true,. launch.json has "preLaunchTask": "npm: watch", but it ignores tasks.json and just runs npm watch without customization.
10. Next we show that launch.json actually knows about tasks.json, but ignores it. Add label to the task: "label": "SomeTaskLabel", and specify that label in launch.json: "preLaunchTask": "SomeTaskLabel".
11. Stop all tasks and press F5 again
12. The debugging session launches correctly

This demonstrates that launch.json can correctly reference task configuration from tasks.json, but decides to ignore it.

P.S. I spent several hours pulling out my hair and I wish VSCode was less ambiguous and did not silently ignore configurations. It should be clear whether the preLaunchTask references a task or an npm script.

P.P.S. This area has more questionable design:
If the task has "path": "123" (but no label), then the following launch setting surprisingly makes things work: "preLaunchTask": "npm: watch - 12". Note that the last character 3 needs to be cut off. This is really a WTF-type behavior. And when using "path": "." you need "preLaunchTask": "npm: watch - " (note the trailing space).

This "preLaunchTask": "npm: watch - <task path with last character cut off>" format is confusing not described anywhere. I prefer proper structure instead of a string with unknown format.