build: upgrade jooq and add junit platform

[enigbe]

What this PR does

With the release of Gradle 9.0.0, we experienced build
failures due to deprecated access to plugin conventions
(JavaPluginConvention).
Ref: Gradle 9.0 release

To address this, we:

• Upgrade jOOQ Gradle plugin from 8.0 to 8.2.2 to
  avoid deprecation warnings when using Gradle 9.0.
  Ref: jOOQ plugin release
• Upgrade jOOQ from 3.17.7 to 3.19.1 to match the
  plugin version upgrade.

Note: We avoid the latest version of jOOQ because it
requires Java 21.

Additionally, we add JUnit Platform Launcher which
is required for JUnit 5 tests in newer Gradle versions.

Related Issues

• LDK-Node Issue #581

cc @tnull

[ldk-reviews-bot]

👋 Thanks for assigning @jkczyz as a reviewer!
I'll wait for their review and will help manage the review process.
Once they submit their review, I'll check if a second reviewer would be helpful.

[enigbe]

Instead of using hard-coded Gradle versions, we extract the version number from the current release.

[ldk-reviews-bot]

🔔 1st Reminder

Hey @wpaulino! This PR has been waiting for your review.
Please take a look when you have a chance. If you're unable to review, please let us know so we can find another reviewer.

[tnull]

Thanks, LGTM!

[tnull]

@enigbe The changes make sense to me, but AFAICT the CI over at enigbe/ldk-node#5 still fails due to expecting Gradle 10? Do we need to fix this here or over on the LDK Node side?

[enigbe]

The changes make sense to me, but AFAICT the CI over at enigbe/ldk-node#5 still fails due to expecting Gradle 10? Do we need to fix this here or over on the LDK Node side?

As is, it is meant to fail until these changes go in.
The fix is on LDK-Node because it is still checking out vss-server with Gradle 8 hard-coded. Here is the passing CI test after introducing commit 430275a that checks out these changes from my fork. Once these changes go in, I can upstream the PR.