Revert jedis 6.0.0 → 5.1.3 and jakarta-persistence-api 3.2.0 → 3.1.0

Both upgrades introduced binary incompatibilities with pre-compiled
Seqera internal libraries and the Micronaut Data layer respectively.

jedis 6.0.0 — same pattern as failsafe:
  All Seqera internal JARs (lib-jedis-pool, jedis-lock,
  lib-cache-tiered-redis, lib-data-store-*-redis, …) were compiled
  against jedis 5.1.4. Forcing 6.0.0 caused silent auth-cache failures
  that broke every test going through the registry proxy.

jakarta-persistence-api 3.2.0 — Micronaut Data compiled against 3.1.0:
  JPA 3.2 added new abstract methods to core interfaces. Micronaut Data
  JDBC (compiled against 3.1.0) throws AbstractMethodError at runtime,
  breaking DB-backed token creation and therefore all registry proxy
  tests that depend on it. The Micronaut BOM manages this at 3.1.0;
  our explicit 3.2.0 was overriding that constraint.

Both are pinned to the versions the pre-compiled JARs expect until the
upstream libraries are updated to support the newer major versions.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: cristianrcv

gradle/libs.versions.toml

@@ -33,9 +33,9 @@ commons-lang3 = "3.20.0"
 failsafe = "3.1.0"
 gson = "2.13.1"
 guava = "33.4.8-jre"
-jakarta-persistence-api = "3.2.0"
+jakarta-persistence-api = "3.1.0"
 jaxb-api = "2.3.1"
-jedis = "6.0.0"
+jedis = "5.1.3"
 kubernetes-client = "24.0.0"
 logback = "1.5.32"
 luaj = "3.0.1"