Update org.junit.jupiter to v5.12.2

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
org.junit.jupiter:junit-jupiter-engine (source)	5.11.4 -> 5.12.2
org.junit.jupiter:junit-jupiter-params (source)	5.11.4 -> 5.12.2
org.junit.jupiter:junit-jupiter-api (source)	5.11.4 -> 5.12.2

---

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 these updates again.

---

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

---

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

[devin-ai-integration]

I've added the org.junit.platform:junit-platform-launcher:1.12.2 dependency as a testRuntimeOnly dependency to both build files.

This resolves the test failures that were occurring due to missing the JUnit Platform Launcher dependency. The error was:
"OutputDirectoryProvider not available; probably due to unaligned versions of the junit-platform-engine and junit-platform-launcher jars on the classpath/module path."

Note that the JUnit Platform uses a different version numbering scheme than JUnit Jupiter, so the correct version is 1.12.2 (not 5.12.2) to match JUnit Jupiter 5.12.2.

All tests and code generation tasks pass successfully with this change.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

[devin-ai-integration]

I've refactored the JUnit dependencies to use the BOM approach as requested:

// Use JUnit BOM for version management
testImplementation(platform("org.junit:junit-bom:5.12.2"))
testImplementation("org.junit.jupiter:junit-jupiter-api")
testImplementation("org.junit.jupiter:junit-jupiter-params")
testRuntimeOnly("org.junit.jupiter:junit-jupiter-engine")
testRuntimeOnly("org.junit.platform:junit-platform-launcher")

This approach has several advantages:

1. Ensures version consistency across all JUnit components
2. Simplifies dependency management by centralizing version information
3. Eliminates the need to manually align versions between JUnit Platform and JUnit Jupiter

The BOM (Bill of Materials) approach is the recommended way to manage JUnit dependencies according to the JUnit documentation.