Already open files are not responding to hover provider when assembler jar is changed

Followup of #98 (closed):

When you open vscode and already have a asm file open (so you left vscode the last time without closing the open file first) no hover information is shown on in that file when also the kickass jar setting is wrong, so kickassembler cannot be found.

While this is a normal/correct behavior, the hover provider should work again whenever the jar setting gets corrected. Unfortunately this is not the case until that file gets changed/saved or reopened (because only then the assemly process gets initiated again.

This ain't an easy task, because i also came accross that "issue" when you use git diff, so the diffed asm file gets opened. But this is maybe worth another issue to investigate.