`workspace/configuration` is impossible to implement on the client side

For reference: https://microsoft.github.io/language-server-protocol/specifications/specification-3-15/#workspace_configuration

The configuration section ask for is defined by the server and doesn’t necessarily need to correspond to the configuration store used be the client.

This makes it impossible for the client to implement workspace/configuration in a generic way. It absolutely requires server-specific knowledge, which turns the "LSP is the solution to the matrix problem" mantra on its head. More specifically:

Rust-analyzer

• section is rust-analyzer
• Client is supposed to return server_settings[ 'rust-analyzer' ]

Gopls

• section is gopls
• Client is supposed to return server_settings

Lua-language-server

• sections are Lua, files.associations and files.exclude
• Client is supposed to return server_settings, and no clue what for the other two

Since a generic implementation is impossible, can we define what section actually means?

Start with the linked LSP 3.15 workspace/configuration specification and compare the Rust-analyzer, Gopls, and Lua-language-server examples in the issue. Determine a protocol-wide meaning for section that allows clients to handle these cases consistently; done means the specification is clarified or revised accordingly.