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.

先解壓附加的 codeql_issue.zip，並在 build-mode=none 下比較已連接的 Boolean 實體化與未連接的未知型別實體化。該 issue 未列出原始碼檔案或測試，因此請從重現案例追蹤相關的 Java 分析進入點。當對 GenericClass.method() 的呼叫能像帶有已知型別參數的呼叫一樣建立連接時，即表示完成。

由索引模型根據 Issue 內容生成。