option to let the language-server timeout->close

The language server is automatically started by the extension as soon as a file with a handled language-identifier is opened.
Within the vscode session only one language server is used.

The issue: often vscode stays open for very long time, but the XML file may be directly closed after it is opened - but the language server will stay open.

I suggest to have a configurable timeout in seconds (0 means never); it would be reset as soon as there is communication with the language server and once reached the language server will be closed, possibly only if the current active editor is not one of the file-types handled.

Note sure if this is common but I have multiple instances of vscode running (different workspaces) and to handle bigger files from time to time I have increased the language server's -Xmx vm args and the language server processes - often only needed for 1 to 3 minutes seem to stay open until I let vscode reload the window.

Start by tracing how the VS Code extension starts and manages its single language-server process when an XML file is opened or closed. Review the extension's configuration and lifecycle entry points, then define the timeout, reset-on-communication, active-editor condition, and 0-means-never behavior; done means the server closes after the configured idle period without affecting active handled files.