Add initial support for defining language server adapters in WebAssem…

…bly-based extensions (zed-industries#8645)

This PR adds **internal** ability to run arbitrary language servers via
WebAssembly extensions. The functionality isn't exposed yet - we're just
landing this in this early state because there have been a lot of
changes to the `LspAdapter` trait, and other language server logic.

## Next steps

* Currently, wasm extensions can only define how to *install* and run a
language server, they can't yet implement the other LSP adapter methods,
such as formatting completion labels and workspace symbols.
* We don't have an automatic way to install or develop these types of
extensions
* We don't have a way to package these types of extensions in our
extensions repo, to make them available via our extensions API.
* The Rust extension API crate, `zed-extension-api` has not yet been
published to crates.io, because we still consider the API a work in
progress.

Release Notes:

- N/A

---------

Co-authored-by: Marshall <marshall@zed.dev>
Co-authored-by: Nathan <nathan@zed.dev>
Co-authored-by: Marshall Bowers <elliott.codes@gmail.com>

.github/workflows/ci.yml

@@ -86,6 +86,12 @@ jobs:
           clean: false
           submodules: "recursive"
 
+      - name: Install cargo-component
+        run: |
+          if ! which cargo-component > /dev/null; then
+            cargo install cargo-component
+          fi
+
       - name: cargo clippy
         shell: bash -euxo pipefail {0}
         run: script/clippy

.gitignore

@@ -10,6 +10,7 @@
 /assets/*licenses.md
 **/venv
 .build
+*.wasm
 Packages
 *.xcodeproj
 xcuserdata/