VS Code: Add some debugging mechanism

[danielbachhuber]

The VS Code extension has crashed in the past. When it does, it can be difficult to figure out what's broken.

Done is:

• We have some debugging mechanism for the VS Code extension that gives us visibility into crashes. This might just be documentation on how to do it, or it might be something we need to add to the code.

[dmsnell]

If it helps, I found a way to get some additional logging that I had previously had a hard time finding: if you open the Output panel there's a dropdown which lets you pick different subsystems within VSCode that leave logging information. I found some messages on Extension Host and Shared to be useful while working on this extension.

Screen.Recording.2023-05-01.at.2.02.39.PM.mov

I also realized that I could call vscode.window.showInformationMessage( "this shows toast messages when console.log doesn't do anything" ) in places running inside the extension to create a "toast" message in the interface.