Incorrect sequence of launch/attach and configurationDone responses

_Things I am planning to work on as part of my exploration of how to debug Indel industrial control systems with Visual Studio Code:_

Currently, the debug adapter protocol is not implemented correctly in that the `launch`/`attach` response is not delayed until after the `configurationDone` response as specified (clearly) in https://github.com/microsoft/vscode/issues/4902#issuecomment-368583522 and (a little less clearly, in my opinion) in the [protocol specs](https://microsoft.github.io/debug-adapter-protocol/overview#launch-sequencing).

I have not seen any adverse effects of this while working in Visual Studio Code, but it would probably be good to correctly implement the protocol anyway.

Start by reading the Debug Adapter Protocol launch sequencing specification and the linked VS Code discussion. Locate the launch and attach entry points and the configurationDone handling in the adapter, then verify that launch/attach responses are delayed until configurationDone has been processed.

Written by the indexing model from the issue text.