refactor(language_server): do not request for worspace configuration when the client does not support it

[Sysix]

Currently working on supporting multiple workspace folder. workspace/didChangeConfiguratoin does not specific the Workspace, so some clients expect to request them.
We need to check if the client support this or fallback to a global configuration change (changing all workspaces).

ChatGPT:

what if workspace/configuration is not supported by the clinet
ChatGPT:
Ah, good follow-up — if the client does not support workspace/configuration, things get more limited and require some careful handling.
🔧 First: Check If the Client Supports It
When your language server receives the initialize request from the client, it includes its capabilities. Look for:

"capabilities": {
  "workspace": {
    "configuration": true
  }
}

If that configuration field is false or missing, then you cannot use workspace/configuration, and the client will only send global settings via workspace/didChangeConfiguration.

[Sysix]

• test(editor): add tests for multi workspace folder setup #10648
• feat(language_server/vscode): support multi workspace folder setups #10515
• refactor(editor): split Config to VSCodeConfig and WorkspaceConfig #10572
• refactor(language_server): make linter independent of Backend #10497
• refactor(language_server): do not request for worspace configuration when the client does not support it #10507 👈 (View in Graphite)
• refactor(language_server): move code actions into own file #10479
• 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 #10507 will create unknown performance changes

_{Comparing 04-19-refactor_language_server_do_not_request_for_worspace_configuration_when_the_client_does_not_support_it (db05a15) with main (9f9e0e5)}

Summary

🆕 36 new benchmarks

Benchmarks breakdown

	Benchmark	BASE	HEAD	Change
🆕	codegen[checker.ts]	N/A	22.1 ms	N/A
🆕	codegen_sourcemap[checker.ts]	N/A	65.1 ms	N/A
🆕	formatter[antd.js]	N/A	708.2 ms	N/A
🆕	formatter[react.development.js]	N/A	8 ms	N/A
🆕	formatter[typescript.js]	N/A	1.1 s	N/A
🆕	isolated-declarations[vue-id.ts]	N/A	58.4 ms	N/A
🆕	lexer[RadixUIAdoptionSection.jsx]	N/A	21.2 µs	N/A
🆕	lexer[antd.js]	N/A	24.8 ms	N/A
🆕	lexer[cal.com.tsx]	N/A	5.9 ms	N/A
🆕	lexer[checker.ts]	N/A	14.9 ms	N/A
🆕	lexer[pdf.mjs]	N/A	3.9 ms	N/A
🆕	linter[RadixUIAdoptionSection.jsx]	N/A	2.7 ms	N/A
🆕	linter[cal.com.tsx]	N/A	1.2 s	N/A
🆕	linter[checker.ts]	N/A	3 s	N/A
🆕	mangler[antd.js]	N/A	15.9 ms	N/A
🆕	mangler[react.development.js]	N/A	293.7 µs	N/A
🆕	mangler[typescript.js]	N/A	39.4 ms	N/A
🆕	minifier[antd.js]	N/A	163.6 ms	N/A
🆕	minifier[react.development.js]	N/A	1.8 ms	N/A
🆕	minifier[typescript.js]	N/A	287.9 ms	N/A
...	...	...	...	...

ℹ️ Only the first 20 benchmarks are displayed. Go to the app to view all benchmarks.

[Sysix]

Merge activity

• Apr 21, 2:11 PM EDT: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Apr 21, 2:11 PM EDT: Sysix added this pull request to the Graphite merge queue.
• Apr 21, 2:17 PM EDT: Merged by the Graphite merge queue.