Debug Launch Config Incorrect Concurrent Operations

## Issue
When executing a debug launch config, _Extension_ for example, there is a dialog that appears stating that errors have occured and prompts the user to either cancel the execution or _Debug Anyways_.

In this screenshot, in the upper righthand side, the dialog window emits an error associated with the launch config. At the bottom of the screen is the terminal where the _package.json_ script is executing and can be observed as not yet being completed.

This results in extension package mismatches if the user selects _Debug Anyways_ and attempts to run through the extension functionality.

If the user has not previously packaged or ran a launch config then no functionality within the extension will work. However, if the user _has_ previously packaged or ran a launch config, i.e, for development changes, then the extension being executed is a cached version and will not contain any development changes.

### Workaround
The current workaround, for the development scenario listed above, is either cancel the launch config execution or select "Debug Anyways" and immediately close the debug extension window. The user must wait until the _package.json_ scripts complete and may then proceed to debugging or executing the extension with the loaded changes.

Inspect the debug launch configuration and the package.json scripts that build or package the extension. Reproduce the concurrent launch, then trace when the debug window starts relative to script completion; done means debugging uses the newly built extension without package mismatches or requiring the documented workaround.

Written by the indexing model from the issue text.