Make ClientConfig fully typed

[rchl]

I'd like ClientConfig to be fully typed. The types could be optional and default to Any.

It would be hard if not impossible to make existing implementation type friendly. Using the new plugin API it could look something like this where we specify config types within a generic of LspPlugin and PluginContext.

from __future__ import annotations

from LSP.plugin import LspPlugin
from LSP.plugin import PluginContext
from lsp_utils import UvVenvManager
from typing import final
from typing import TypedDict
from typing_extensions import override


class PluginSettings(TypedDict):
    server_binary: str
    settings: ...


@final
class RuffLsp(LspPlugin[PluginSettings]):
    uv_venv_manager: UvVenvManager | None = None

    @classmethod
    @override
    def install_async(cls, context: PluginContext[PluginSettings]) -> None:
        if not cls.uv_venv_manager:
            cls.uv_venv_manager = UvVenvManager(cls.name, 'pyproject.toml', cls.plugin_storage_path.parent)
            if cls.uv_venv_manager.needs_install_or_update():
                cls.uv_venv_manager.install()

    @classmethod
    @override
    def additional_variables(cls, context: PluginContext[PluginSettings]) -> dict[str, str]:
        if cls.uv_venv_manager:
            return {
                'server_path': str(cls.uv_venv_manager.venv_bin_path / 'ruff')
            }
        return {}


def plugin_loaded() -> None:
    RuffLsp.register()


def plugin_unloaded() -> None:
    RuffLsp.unregister()

The problem with that is that the default value for the generic is only supported from python 3.13. Without it one would have to always specify generic explicitly (even if it's just Any).

Even with support for default value, we'd still likely need to create a replacement for ClientConfig so that we can properly type settings or any root setting not explicitly defined in ClientConfig (supported through the __getattr__ implementation).

Then there is also a question of whether anyone would have time and patience to define all the settings in TypedDict in addition to maintaining sublime_package.json and also ensure that those are in sync. For that we could potentially create some script but it would still have to be run to generate types.