Fix native LSP

[hugoclrd]

The LSP is exposed through two interfaces, the Wasm bridge (for vscode) and the native bridge.
The native bridge has been poorly maintained and suffers from major bugs, such as significant lag and eventual desynchronization with the editor's state.

This bug fix will require some investigation, bug fixing, unit, and integration tests to make sure that Clarity developers can use the IDE of their choice

[andresgalante]

at the moement @jbencin working on zed and helix, we want to make sure it works on Neovim too.

[jbencin]

The sync problem is fixed in #1828. There is also another known bug in the Native LSP (#1829), and possibly others. I will make a separate ticket for each new issue I find, this one can be closed when #1828 is merged

at the moement @jbencin working on zed and helix, we want to make sure it works on Neovim too

The fixes I've made in Clarinet will work for all non-VSCode editors. To get Clarity support in an editor, you just need to do the following:

• A config file entry or small plugin to tell it how to use the LSP
• Configure it to use the tree sitter git repo for syntax highlighting
• Some syntax highlighting queries specific to the editor

I've done that for Helix and Zed so far. There is a config for Neovim also that I want to try out and update if necessary