Support all new 3.17 features (except for notebooks)

[ebkalderon]

Added

• Add support for textDocument/inlineValue.
• Add new features to workspace/symbols and support workspaceSymbol/resolve.
• Add support for HTML tags in MarkdownClientCapabilities.
• Add support for collapsed text in folding.
• Add support for trigger kinds in code action requests.
• Add support for position encoding (not sure if safe to remove support for unofficial UTF8-offsets extension now?)
• Add support for relative patterns in FileSystemWatchers
• Add support for type hierarchies.
• Stabilize CodeActionKind::SOURCE_FIX_ALL.

Changed

• Stabilize LSPAny, LSPObject, and LSPArray type aliases.
• Stabilize support for textDocument/inlayHint.
• Stabilize all parts of semantic token support marked proposed.
• Stabilize completion label item details support.
• Stabilize support for insert text mode on CompletionItems.
• Stabilize stale client request handling capability.

Fixed

• Add missing CompletionList client capability.
• Add some missing API documentation.
• Update protocol reference links in README.md.

There was a lot of work done here to bring lsp-types to actually support the 3.17.0 specification (see official changelog). I chose to not add in notebook support myself, since there seems to be a draft PR already open which tackles that (#229). This work should take care of everything else, though.

Closes #238.
Closes #251.
Closes #252.
Blocks ebkalderon/tower-lsp#352.

[ebkalderon]

@Marwes Just wanted to send a gentle ping requesting a review. Sorry to do this directly; I only wanted to let you know that there are several downstream projects currently awaiting LSP 3.17.0 support to land. Any feedback would be appreciated. Thanks! ❤️

[krobelus]

I sometimes point my project to a temporary fork of lsp-types, cargo makes it easy to use git dependencies.

[ebkalderon]

@krobelus I do too, but only on personal projects or in binary-only crates. I'd hardly like to do that in tower-lsp as that could potentially break downstream users of my library who either (a) depend on lsp-types directly (despite tower-lsp providing a re-export of lsp-types expressly for the purpose of reducing breakage) and/or (b) rely on other third-party libraries which depend on published versions of lsp-types.

I could put a big disclaimer on such a release, requesting developers of binary crates depending on tower-lsp add a [patch] at the top level of their Cargo workspace forcing all instances of lsp-types in the dependency tree to point towards the Git repo, but this would be very disruptive. I would like to avoid that, if I can help it.