Implement fallback handler for */resolve requests

[fendor]

We had multiple reports, where resolve requests (such as completion/resolve and codeAction/resolve) are rejected by HLS since the _data_ field of the respective LSP feature has not been populated by HLS.
This makes sense, as we only support resolve for certain kinds of CodeAction/Completions, when they contain particularly expensive properties, such as documentation or non-local type signatures.

So what to do? We can see two options:

1. Be dumb and permissive: if no plugin wants to resolve a request, then just respond positively with the original item! Potentially this masks real issues, but may not be too bad. If a plugin thinks it can handle the request but it then fails to resolve it, we should still return a failure.
2. Try and be smart: we try to figure out requests that we're "supposed" to resolve (e.g. those with a data field), and fail if no plugin wants to handle those. This is possible since we set data. So as long as we maintain the invariant that only things which need resolving get data, then it could be okay.

In 'fallbackResolveHandler', we implement the option (2).

Supersedes #4463 and presumably fixes #4451 and #4467

[fendor]

This pattern matching is bad for long-term maintenance. Anyone an Idea on how to improve this? If we do a string comparison ala isSuffixOf "/resolve" (someMethodToMethodString ...), then I don't see how to actually implement the check, as we need a proof for JL.HasData_ p (Maybe a) where p ~ MessageResult s.

I have an idea for DRY'ing up noResolveData params via Dict, but it introduces a bit of complexity I am not sure is worth it.