Bridge the ide/api.lsp services for ide/lsp.client

[lahodaj]

Discussed before, if a module provides implements ide/api.lsp services, it might be good to use them internally in the IDE. This is a bit more polished prototype doing that. It is done by having an internal LS server bridging the services to lsp.client. Note that the data are not serialized, they are just converted from the ide/api.lsp structures to the LS structures, and then to the IDE structures.

CC @jtulach

[jtulach]

@lahodaj thank you. I can confirm your patch does work. It displays errors/hints and shows code completion. All of that with just a three line change in Enso layer.xml:

However navigator is broken. Without your PR the structure is visible (thanks to #7483), but with your PR it disappears...

[matthiasblaesing]

@jtulach the missing navigator should be fixed by #7757, the feature was broken by #7483. So test this together with current master.

[lahodaj]

I've added bridging for documentSymbols, which should fix the navigator (and should also give you breadcrumbs for free, I think). I think this issue with the navigator demonstrates the existing approach is quite fragile.

I've also moved the annotation to api.lsp, as requested elsewhere.

[jtulach]

Enso works with the current state of the PR:

• errors
• code completion
• navigator

I don't see breadcrumbs, but that OK. Please get this into a release!

[lahodaj]

Unless there are objections, I'll squash and merge in the next day or so.