refactor: make LSP definitions independent from language

[horriblename]

There are several LSPs that are used by multiple languages, we should find a way to decouple LSP config definitions from their language modules. The main approach under consideration is #1195 (comment)

[snoweuph]

an example would be tsgo which you prolly want in javascript, typescript, svelte, and vue¹

another example would be with scss² and css

Footnotes

1. languages/vue: init #1479 languages/ts: add vtsls support for vue #1322 add vue support for ts_ls #1310 ↩

2. languages/scss: init #1393 ↩

[snoweuph]

The approach would prolly also need to support overriding LSP options for specific languages 🤔
like passing tsgo some extra option when im in a vue file to some lib (just an example, dunno if you actually need to do something like that)

[sjcobb2022]

Quick question for the changes made in #1514

I may be fully wrong in saying this (and please correct me if I am wrong), but since LSPs can support multiple filetypes technically, should the filetype responsibility not be in the preset as opposed to at the language module level?

[snoweuph]

We are keeping it simmilar to the old API. As for supporting multiple language modules using the same LSP. That was the main reason for the change, as thats now possible. See the terraform-ls and tofu-ls for example

You could always write your filetypes into the vim.lsp.servers.<name>.filetyes but we dont want to add the defaults on the presets, as people might not want the LSP running on all its theoreticly support filetypes and are used to the language module APIs