build(deps): update dependency org.eclipse.jdt:org.eclipse.jdt.core to v3.39.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
org.eclipse.jdt:org.eclipse.jdt.core (source)	3.38.0 -> 3.39.0

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[SirYwell]

It looks like JDT dropped support for targeting Java 1.7. So the minimum compliance level must be 8 now.

[I-Al-Istannen]

public class Action<Request extends BroadcastRequest<Request>, ShardRequest> {
    private final Request request;
    protected void performOperation(final int shardIndex) {
        ShardRequest shardRequest = newShardRequest(request);
        shardRequest.setParentTask(foobar);
    }
}

This is MWE for the failing stackoverflow test. The new version of JDT does not have a variable binding for the setParentTask method call, as it does not seem to find the definition of the local variable.
Prerequisites:

• Request is a recursive generic
• request is passed to newShardRequest
• The input of setParentTask is an undefined variable (otherwise the declaring type resolves to null even in older JDT versions)

I am not sure if this can reasonably be construed a JDT bug. There is basically nothing valid left in the code, though the connection to the variable feels quite easy to make…