Fix file-watching mechanisms

[JonatanWaern]

Currently, the file-watchers setup by the language server do not seem to work correctly towards (at least) vscode client. It is uncertain if this is because of how we register the pattern or not. At the very least the client responds with a successful response to the capability registration.

Impacts dml_compile_commands changing after server started.

[JonatanWaern]

Attempts to fix this at #122 , so far no success

[JonatanWaern]

#122 now is at the point where this works in some cases

There is an upstream issue in how vscode handles file-watching on NFS disks, more-or-less meaning we cannot rely on vscode client to accurately report changes for us. (microsoft/vscode#250346, microsoft/vscode#201103)

Per lsp-spec, we should rely on the client providing the LS with change events on watched files. However seemingly the standard workaround is to do file-watching on server-side in some cases anyway.