Java: Generic Class Methods not connected when type parameter is unknown (build-mode=none)

The introduction of `build-mode=none` has been very helpful for us. This allows us to create (partial) CodeQL databases, without being forced to fully resolve (maven) dependencies. Sometimes this is convenient because some dependencies might not be easily resolvable.

That said, we also see many examples of Generic Classes and Methods in our codebases. Unfortunately, we cannot analyse (calls to) Generic Methods that are instantiated with type parameters that are unknown.

Note that, while the code of the type parameter `T` is unavailable, the code of the `GenericClass` *is* available.

## Example pseudo code
```
class GenericClass {
public method() { ... };
};

GenericClass i1 = new GenericClass<>();
i1.method(); // not connected
GenericClass i2 = new GenericClass<>();
i2.method(); // connected
```

See attached [codeql_issue.zip](https://github.com/user-attachments/files/20345107/codeql_issue.zip) zip file for a more thorough analysis of the issue.

Start by unpacking the attached codeql_issue.zip and comparing the connected Boolean instantiation with the unconnected unknown-type instantiation under build-mode=none. The issue names no source files or tests, so trace the relevant Java analysis entry point from the reproduction. Done means calls to GenericClass.method() are connected like calls with a known type parameter.

Written by the indexing model from the issue text.