Parser server error handling improvements

[jonsequitur]

This PR:

• Moves the notebook parser server out of the Documents package and into dotnet-interactive.
• Removes the NotebookErrorResponse type and sends error info to log output rather than trying to communicate them over the main channel.
• Fixes logic that might result in the parser server continuing to run even after significant errors are encountered or someone has tried to shut down the process gracefully.
  • This fixes a repro for Dotnet-interactive processes continue running even after shutdown/restart kernel commands issued form the VSCode UI and quitting the VSCode app #1005 and Closing VS Code notebook orphans dotnet processes on MacOS #1650 which would happen only when multiple non-.NET Interactive Jupyter notebooks are opened at the same time.

[shyamnamboodiripad]

This is orthogonal - but should our exception messages be localized?

[jonsequitur]

We don't typically localize exception messages.

[shyamnamboodiripad]

My assumption was that exception messages should be localized if they can ever end up being displayed to the end user...

For C#, we would display localized messages for compilation errors etc., would we not? It seems strange that we would always display English messages for any errors that originate within .NET Interactive itself...

[shyamnamboodiripad]

Was this intentional or something temporary that you meant to revert?

[jonsequitur]

Ah, I didn't mean to revert it. The logic looked weird so I was checking if it's actually needed.

[shyamnamboodiripad]

This is just appending ellipsis if the content happens to span multiple lines (since we are trimming out all lines except the first one). I think it should be preserved.

[jonsequitur]

I'll replace this in my next PR.