[LS] Checker errors persisting after they have been resolved

[jribbink]

Problem

For some reason, under certain conditions the language server will break and errors will persist even after they are resolved. This is a pretty recent issue and is affecting users on the playground. This happens when the contract has not yet been deployed so it appears that this may be simply one error presenting as another.

Steps to Reproduce

Do the same thing I did in the gif on a fresh instance of the playground. (the TX used is the default one)

Acceptance Criteria

Errors disappear after user resolves them.

Context

Breaks Playground

[turbolent]

@jribbink Can you reproduce this in e.g. VS Code? This might be caused by how the LS is integrated into the Playground