LSP: make sure we always handle VSCode configuration change

In https://tezos-dev.slack.com/archives/C04EM6W78A0/p1701376226760309?thread_ts=1699898794.497219&cid=C04EM6W78A0 @DK318 mentions that sometimes changes of VSCode configuration were not handled by our LSP before the VSCode restart (so even the LSP restart was not enough).

We need to understand why this can happen