feat(language_server): support textDocument/diagnostic

[Sysix]

This PR introduces the support for textDocument/diagnostics. This will be preferred over the other way around textDocument/publishDiagnostics
It is a newer concept between language server and the clients (editors).

Diagnostics are currently published by the server to the client using a notification. This model has the advantage that for workspace wide diagnostics the server has the freedom to compute them at a server preferred point in time. On the other hand the approach has the disadvantage that the server can’t prioritize the computation for the file in which the user types or which are visible in the editor. Inferring the client’s UI state from the textDocument/didOpen and textDocument/didChange notifications might lead to false positives since these notifications are ownership transfer notifications.

The specification therefore introduces the concept of diagnostic pull requests to give a client more control over the documents for which diagnostics should be computed and at which point in time.

https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_pullDiagnostics

For our server, we need one more feature.

The workspace/diagnostic/refresh request is sent from the server to the client. Servers can use it to ask clients to refresh all needed document and workspace diagnostics. This is useful if a server detects a project wide configuration change which requires a re-calculation of all diagnostics.

This is needed because in the current implementation we re-lint the opened files when some .oxlintrc.json configuration is changed or fix_kind server configuration. Instead of re-linting, the server will send this request to the client.

---

This will be a breaking change for other clients which are sending the run = onType | onSave configuration, but are supporting all needed specs for the pull diagnostics mode. The client should instead implement their own configuration and sending the textDocument/diagnostics to the server when needed.

---

The cargo patches are needed, because of a typo in the lsp-types project. The community created a fork and fixed it already for us: tower-lsp-community/ls-types@71ca29b
The tower-lsp-server needed an update too, or else we could not use the fixed version. I created a PR here: tower-lsp-community/tower-lsp-server#52 and used the commit ID to patch it here.

[Sysix]

• feat(language_server): support textDocument/diagnostic #11447 : 2 dependent PRs (#11414 , #11486 ) 👈 (View in Graphite)
• refactor(language_server): convert only once uri to path when creating ServerLinter #11503
• main

---

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

• 0-merge - adds this PR to the back of the merge queue
• hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[codspeed-hq]

CodSpeed Instrumentation Performance Report

Merging #11447 will not alter performance

_{Comparing 06-02-feat_language_server_support_textdocument_diagnostic_ (e627309) with main (4ca659c)}

Summary

✅ 38 untouched benchmarks

[camc314]

cc @Boshen is this ok? i remember you mentioning using git tags means cargo can't cache it

[Sysix]

@Boshen want to make sure you agree to this before, before resolving the conversation and starting the queue

[graphite-app]

Merge activity

• Jun 13, 11:40 AM UTC: This pull request can not be added to the Graphite merge queue. Please try rebasing and resubmitting to merge when ready.
• Jun 13, 11:40 AM UTC: Graphite disabled "merge when ready" on this PR due to: a merge conflict with the target branch; resolve the conflict and try again..
• Jun 13, 11:40 AM UTC: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Jun 19, 8:53 PM UTC: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Jun 20, 12:27 PM UTC: This pull request can not be added to the Graphite merge queue. Please try rebasing and resubmitting to merge when ready.
• Jun 20, 12:27 PM UTC: Graphite disabled "merge when ready" on this PR due to: a merge conflict with the target branch; resolve the conflict and try again..
• Jun 20, 12:27 PM UTC: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.

[Sysix]

After the integration with tsgolint, the client can not tell when it is the right time to request for diagnostics.
When tsgolint supports linting on memory file too, I will relook into this feature. Closing for now, but keeping the branch alive