Refactoring to use logging framework

[alt-romes]

To implement OutputEvents we may need to capture the stdout and stderr of the debuggee. However, if the DAP server is also outputting to stdout and stderr its messages will be mixed up with the debuggee's.

This commit introduces a logging action to ensure it is possible to redirect all of the DAP server's output to a particular handle, thereby separating it from the debuggee.

Fixes #9

[dmjio]

Yea I think this is fine. Curious did you have an issue with the global lock?

I think the intention was to allow both the debugger and server to log to the same Handle, so the server could observe output, and not have it be interleaved. So whoever grabs the lock will always append a message with a newline \n, so from the user's perspective they might see something like this on the server

[DEBUGGER] Breakpoint set
[SERVER] Sending Breakpoint message
[DEBUGEE] Received breakpoint
[SERVER] Received event
[SERVER] Sending message

But we also want to forward the debugger output bytes to VSCode so people can see what the debugger is up to. I don't think we made it that far with the dap-estgi-server.

[alt-romes]

I didn't observe any problems with the lock.

Indeed, with this we implemented support for logging the debugger's output to vscode!

FWIW we chose the same logging library as HLS, and Matthew was already familiar with it IIRC

[alt-romes]

Please land it if you think it's ready.

[dmjio]

That is awesome the debugger output is visible in VSCode now 😎