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.

Comece descompactando o codeql_issue.zip anexado e comparando a instanciação conectada de Boolean com a instanciação não conectada de tipo desconhecido em build-mode=none. O issue não nomeia arquivos-fonte nem testes; portanto, rastreie o ponto de entrada relevante da análise de Java a partir da reprodução. O trabalho estará concluído quando as chamadas a GenericClass.method() estiverem conectadas como as chamadas com um parâmetro de tipo conhecido.

Escrita pelo modelo de indexação a partir do texto da issue.