fix: switch to gen-lsp-types

[ribru17]

Summary

gen-lsp-types is an alternative to the lsp-types crate, with types generated via codegen from the official LSP Metamodel for correctness and completeness.

lsp-types issues fixed in gen-lsp-types:

• Add LSP 3.18 SnippetTextEdit support (proposed) gluon-lang/lsp-types#310
• Eq and Hash for all Param/Result types? gluon-lang/lsp-types#308
• The new Uri type in 0.96.0 is hard to use and have almost no interoperability gluon-lang/lsp-types#284
• Why type names of this crate don't follow the spec ? gluon-lang/lsp-types#278
• Auto-generate Protocol Bindings gluon-lang/lsp-types#277
• Derive Default for CodeActionOptions gluon-lang/lsp-types#260
• many types don't derive Hash even though they can gluon-lang/lsp-types#245
• FoldingRange.kind is limited gluon-lang/lsp-types#93

Test Plan

All affected test fixtures updated. Most (all?) are just field reordering, struct type name renaming

[ribru17]

Looks like jj does not respect .gitattributes, so the CRLF tests were changed to use LF line endings... will revert those changes

[MichaReiser]

As a note. @ribru17 is the author of the crate. The crate is very new.

[MichaReiser]

Thanks for doing this work. This is a major change, and the crate still undergoes frequent changes. Given that we don't really experience any of the pains listed in the PR summary, I prefer, at least for now, to keep our very stable lsp-types crate. Switching to your crate is something we can consider once it's more established.

Don't get me wrong. I'm very interested in a successor to the lsp_types crate. It's just that I think this is a bit too early days for us.

[ribru17]

I totally understand, I was pretty overzealous with this PR 😄 let me know if/when you change your mind and I'll be happy to pick this up again. (PS, you may be interested in following rust-lang/rust-analyzer#22115)