fix: Fix crash on handling parameterized ProblemReferenceBinding

[slarse]

Fix #3951

The problem is described in the issue. It's very rare for JDT to parse a parameterized type reference to a ProblemReferenceBinding (even when the actual referenced type can't be resolved). In the particular case of error code 15 (using a type that isn't closable on a try-with-resources), it does however resolve the reference to a ProblemReferenceBinding with type parameters in the name, which caused the crash.

This PR does not attempt to parse the type arguments, it only fixes the crash and lets the pre-existing logic for creating type references from problem bindings do its thing. In other words, a type reference is created with the correct simple name, and that's about it. A warning that the type arguments are ignored is also issued.

I found a way to actually resolve the correct type binding in the particular corner case represented in the test case I added, which I may add in a later PR as that coincidentally triggers the long-standing bug reported in #3708.

[slarse]

Waiting for #3966

[slarse]

This turns out to be a massive pain. Resolving anything beyond the simple name of the type is really error-prone, as JDT provides next to no information.

[monperrus]

Thanks @slarse

I feel your pain, having myself spent a lot of time workarounding ProblemReferenceBinding