lsp: Update LSP linting to run incrementally after file change

[charlieegan3]

Fixes to #1133

This PR is a large refactoring of the language server diagnostics loops. Changes:

• when the contents of a file with aggregate violations changes, this no longer triggers a full workspace lint
• when the contents of any file changes, the aggregate rule state is now cached on the server and the results of this update, in addition to the full global state, is used to perform a linting run of all files but only linting for aggregate rules.
• new tests have been added to cover this functionality and the underlying functionality which these server changes depend on in the linter.
• server tests moved to new files since they are very long.
• increased timeouts for go test when running in go test -race https://go.dev/doc/articles/race_detector#Runtime_Overheads
• updated the cache to allow partial updating of diagnostics based on the relevant rules.

[anderseknert]

Code looks good to me! Only complaint would be all the changes not directly related to solving the issue, but they are also good changes, so why not! Might have been better off in separate PRs though :)

I'm excited to try this out!

[anderseknert]

👍

[anderseknert]

I've tried this now and it's a huge improvement 👏 No more lag or even freezes, but most things just show up right away, and the aggregate violations a little later. This is great!

[charlieegan3]

aggregate violations a little later

Yeah, I actually think that we are in a position to correct that, but I'd need to do some more testing. This is because for a per-file run, only the non agg rules are run to improve performance. Since we know that a full workspace agg rule run will take place immediately after with the updated aggregate state.

I think the solution is to provide all aggregate data but for the current file, and then run all rules in the per file lint run. It should be simple enough, but something I think might approached in another PR....