chore(deps): update dependency org.junit.jupiter:junit-jupiter to v6

[dd-octo-sts]

This PR contains the following updates:

Package	Type	Update	Change
org.junit.jupiter:junit-jupiter (source)	dependencies	major	5.14.4 → 6.1.3

🚨 Gradle Security Update (Major) - CRITICAL

This PR addresses critical severity security vulnerabilities in Gradle dependencies with major version changes.

---

• Version Upgrader Overview

• Questions or feedback? Ask in #dep-health-support

🤖 Generated by ADMS (Automated Dependency Management System)

🚨 Gradle Security Update (Major) - HIGH

This PR addresses high severity security vulnerabilities in Gradle dependencies with major version changes.

[datadog-prod-us1-4]

✨ Unblock PR with BitsAI

⚠️ Warnings

❌ Your PR has failed checks. Please review the issues below and take necessary action before merging.

🚦 2 Pipeline jobs failed

CodeQL Advanced | Analyze (java-kotlin) — 🔧 Needs a code fix, caused by this PR

View more details · View in GitHub Actions

Dependency resolution error: 'org.junit.jupiter:junit-jupiter:6.1.3' requires JVM runtime version 17 or newer, incompatible with current setup (JVM version 8).

DataDog/dd-instrument-java | build — 🔧 Needs a code fix, caused by this PR

View more details · View in GitLab

📋 Copy fix prompt

CI on my pull request is failing. Help me find and fix the root cause of each failing job below — they were flagged as caused by changes in this PR, so focus on the diff. For each job, explain the failure and propose a fix.

Before you start, set up the Datadog software-delivery tooling so you can
query the CI data yourself:

1. Check whether you already have the Datadog software-delivery MCP tools
   (e.g. a `search_datadog_ci_pipeline_events` tool) and the `unblock-pr` skill.
2. If either is missing, STOP and ask me for permission before installing
   anything. Do not install or run anything until I have said yes.
3. Only with my explicit approval, set up the Datadog software-delivery MCP
   server and skills by following:
     https://docs.datadoghq.com/getting_started/software_delivery_mcp_tools/
   then restart so the skill is picked up.
4. If I decline, skip all of the above and work from the context below alone.

Then run /unblock-pr — it will pull the CI data itself. The job context below is what we already know.

If /unblock-pr is not available — because I declined the setup above, or it did not install — work from the context below instead.

Datadog has already classified this failure as caused by changes in this PR.
Take that as given and work the fix:

1. Locate the change. Diff this branch against its base and find the change
   that produces this error. Explain the mechanism, don't just name a file:
     git fetch origin && git diff $(git merge-base origin/main HEAD)...HEAD
2. Reproduce it locally. Run the failing job's command or test before
   proposing anything.
3. Propose the smallest fix that addresses the root cause — not a workaround,
   not a broadened assertion, not a disabled or skipped test.
4. Re-run the same command to confirm, and say exactly what you ran.
5. If the failure turns out to be intermittent rather than deterministic, say
   so plainly instead of "fixing" it — that is a flaky test, and patching it
   hides the problem.

If the right move is to re-run the job rather than change code, use the job
link in the context below. For GitHub Actions: `gh run rerun <run-id> --failed`,
where the run ID is the number after `/runs/` in that URL (not the trailing
number, which is the job ID).

Branch: engraver-auto-version-upgrade/renovate/major-junit.jupiter

CodeQL Advanced | Analyze (java-kotlin)
Commit: 56fe97e476ec86924ade82d206e44f026269287f
Error (code / build):
Dependency resolution error: 'org.junit.jupiter:junit-jupiter:6.1.3' requires JVM runtime version 17 or newer, incompatible with current setup (JVM version 8).
CI job: https://github.com/DataDog/dd-instrument-java/actions/runs/34092305551/job/101648191217

Useful? React with 👍 / 👎

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 56fe97e | Docs | View more details | Give us feedback!}

[mcculls]

We cannot upgrade to JUnit 6 because we need to test on Java versions before 17