feat: Add default configuration for KCL language server

[arichtman]

Adds a default configuration for KCL's language server.

I'm not sure where else this needs to be added.
It looks like the --health argument operates dynamically enough.
Where in the tests might a test for this go?
Should I add something to the release notes?

Fix #13147

[the-mikedavis]

Generally we don't accept language definitions that don't also have syntax highlighting. Language server configurations can go in https://github.com/helix-editor/helix/wiki/Language-Server-Configurations

[uncenter]

I came across nvim-treesitter/nvim-treesitter#7657 the other day as I was looking to upstream something to nvim-treesitter, so looks like there is a maintained Tree-sitter grammar you can use! https://github.com/kcl-lang/tree-sitter-kcl

[arichtman]

Added highlighting 😊

[uncenter]

Some suggestions on how to improve the queries :)

[uncenter]

Some/all of these can be under keyword.operator instead.

[arichtman]

I moved the ones commented here, or did you mean all of them under @operator ?

[uncenter]

Suggested change

	(identifier) @property))
	(identifier) @property))

property isn't an official scope for Helix, maybe variable.other.member is fitting if this node matches the description of "Fields of composite data types (e.g. structs, unions)"?

[arichtman]

Wow, awesome @uncenter - but this highlighting.scm is verbatim from the tree-sitter-kcl repository. I'm guessing we should upstream these?

[uncenter]

Wow, awesome @uncenter - but this highlighting.scm is verbatim from the tree-sitter-kcl repository. I'm guessing we should upstream these?

It's a little complicated because every Tree-sitter based editor does things differently. The original queries here (from the upstream repository) look like they are intended for usage in Neovim, whereas Helix uses some different scopes in its themes so we have to change it up a bit (no need to upstream these changes back since the changes will be specific to Helix).