Ensure that workspace/Configuration is always used with editors that support it

[Techatrix]

It turns out that ZLS has been relying on the outdated workspace/didChangeConfiguration request even in editors that supported workspace/Configuration.

This change may require updating the user config to ensure ZLS options set in the editor config continue to work.

Sublime Text

{
  "clients": {
    "zls": {
      "enabled": true,
      // ...
      "settings": {
-        "zig_exe_path": "/path/to/zig_executable"
-        "enable_build_on_save": true
+        "zls": {
+          "zig_exe_path": "/path/to/zig_executable"
+          "enable_build_on_save": true
+        }
      }
    }
  }
}

Helix

[language-server.zls]
command = "/path/to/zls_executable"
- config.enable_build_on_save = true
- config.zig_exe_path = "/path/to/zig_executable"
+ config.zls.enable_build_on_save = true
+ config.zls.zig_exe_path = "/path/to/zig_executable"

Zed

{
  "lsp": {
    "zls": {
      "binary": {...},
      "settings": {
-       "enable_build_on_save": true,
-       "zig_exe_path": "/path/to/zig_executable"
+       "zls": {
+         "enable_build_on_save": true,
+         "zig_exe_path": "/path/to/zig_executable"
+       }
      }
    }
  }
}

Neovim

lspconfig.zls.setup {
  cmd = { '/path/to/zls_executable' },
  settings = {
-   enable_build_on_save = true,
-   zig_exe_path = '/path/to/zig_executable'
+   zls = {
+     enable_build_on_save = true,
+     zig_exe_path = '/path/to/zig_executable'
+   }
  }
}

[Techatrix]

Reverted in 1656b5d until ziglang/vscode-zig#442 has been merged to make this work with the VS Code extension for Zig.