add more context on why LSP server start failed.

[heejaechang]

Currently, we only get callstack when it failed, but the callstack is very generic and same for all causes, so no actionable data except the fact it got failed.

it would be very helpful if it contains other context such as why LSP server is started (interpreter changes, from status bar or command palette, trusted/untrusted? folder or single file mode, restart command is issued, local or remote, what kind of remote and etc)

anything that can inform us code path it took to start new server so we can repro the failure.

[heejaechang]

@karthiknadig any progress?

[karthiknadig]

Sorry, no. I could not get to this for august.