Uncap most remaining dependencies (#3073)

This commit relaxes the upper bounds on several dependencies that were previously hardcapped to specific versions:
- com.google.protobuf to [3.25.5,) and [3.17.3,)
- org.apache.beam to [2.72.0,)
- io.github.ss-bhatt to [1.0.0,)
- io.protostuff to [1.8.0,)
- redis.clients:jedis to [7.4.1,)
- org.junit.jupiter and org.junit.platform to [5.6.2,) and [1.6.2,)
- org.jcommander to [2.0,)
- org.jline to [3.0,)
- jakarta.servlet to [6.0,)

Upgrading to the modern versions of jline introduced a breaking change where DefaultParser().parse(line, line.length()) strips trailing spaces when using the default ParseContext.UNSPECIFIED. This caused the autocompletion to misbehave and tests to fail. This commit fixes ShellCommandTest.java by explicitly passing ParseContext.COMPLETE when parsing test strings to perfectly mimic the real-world JLine completion context.

Additionally, SqlIntegrationTestSuite was migrated to JUnit 5's @Suite annotation, fixing a NoClassDefFoundError introduced by uncapping the JUnit Platform dependencies, and the test suite was re-integrated into the standard :build lifecycle.

The following dependencies remain explicitly capped:
1. Hibernate & Jakarta Persistence (Blocked by -Werror):
   These are held back because newer Jakarta Persistence versions deprecate executeUpdate(), setMaxResults(), and getResultStream() on Query.
   - org.hibernate.orm:hibernate-core:7.3.4.Final
   - org.hibernate.orm:hibernate-hikaricp:7.3.4.Final
   - org.hibernate.orm:hibernate-ant:7.3.4.Final
   - jakarta.persistence:jakarta.persistence-api:[3.2.0,4.0.0)

2. Netty (Blocked by abandoned v5):
   Netty 5.0.0 was an experimental release abandoned in 2015. We explicitly cap beneath 5.0.0 so Gradle doesn't resolve dead-end alphas.
   - io.netty:netty-codec-http:[4.1.59.Final, 5.0.0)!!
   - io.netty:netty-codec:[4.1.59.Final, 5.0.0)!!
   - io.netty:netty-common:[4.1.59.Final, 5.0.0)!!
   - io.netty:netty-handler:[4.1.59.Final, 5.0.0)!!
   - io.netty:netty-transport:[4.1.59.Final, 5.0.0)!!
   - io.netty:netty-buffer:[4.1.59.Final, 5.0.0)!!

3. Google API Services:
   Capped beneath their respective unstable beta/v1b4 versions:
   - com.google.apis:google-api-services-dataflow:[v1b3-rev20240430-2.0.0, v1b4)!!
   - com.google.apis:google-api-services-dns:[v1-rev20240419-2.0.0, v2beta)

The lockfiles have been fully regenerated and all test suites ran successfully against the latest available transitive versions.

core/src/test/java/google/registry/schema/integration/SqlIntegrationTestSuite.java

@@ -52,9 +52,8 @@ import google.registry.schema.registrar.RegistrarDaoTest;
 import org.junit.jupiter.api.AfterAll;
 import org.junit.jupiter.api.BeforeAll;
 import org.junit.jupiter.api.Test;
-import org.junit.platform.runner.JUnitPlatform;
 import org.junit.platform.suite.api.SelectClasses;
-import org.junit.runner.RunWith;
+import org.junit.platform.suite.api.Suite;
 
 /**
  * Groups all JPA entity tests in one suite for easy invocation. This suite is used for
@@ -68,20 +67,8 @@ import org.junit.runner.RunWith;
  * <p>Note that with {@link JpaIntegrationWithCoverageExtension}, each method starts with an empty
  * database. Therefore, this is not the right place for verifying backwards data compatibility in
  * end-to-end functional tests.
- *
- * <p>As of April 2020, none of the before/after annotations ({@code BeforeClass} and {@code
- * AfterClass} in JUnit 4, or {@code BeforeAll} and {@code AfterAll} in JUnit5) work in a test suite
- * run with {@link JUnitPlatform the current JUnit 5 runner}. However, staying with the JUnit 4
- * runner would prevent any member tests from migrating to JUnit 5.
- *
- * <p>This class uses a hack to work with the current JUnit 5 runner. {@link BeforeSuiteTest} is
- * added to the front of the suite class list and invokes the suite's setup method, and {@link
- * AfterSuiteTest} is added to the tail of the suite class list and invokes the suite's teardown
- * method. This works because the member tests are run in the order they are declared (See {@code
- * org.junit.platform.engine.support.descriptor.AbstractTestDescriptor#addChild}). Should the
- * ordering changes in the future, we will only get false alarms.
  */
-@RunWith(JUnitPlatform.class)
+@Suite
 @SelectClasses({
   // BeforeSuiteTest must be the first entry. See class javadoc for details.
   BeforeSuiteTest.class,

core/src/test/java/google/registry/tools/ShellCommandTest.java

@@ -40,6 +40,8 @@ import java.util.Arrays;
 import java.util.List;
 import org.jline.reader.Candidate;
 import org.jline.reader.LineReaderBuilder;
+import org.jline.reader.ParsedLine;
+import org.jline.reader.Parser;
 import org.jline.reader.impl.DefaultParser;
 import org.jline.terminal.Terminal;
 import org.jline.terminal.impl.DumbTerminal;
@@ -176,12 +178,13 @@ class ShellCommandTest {
     jcommander.addCommand("testCommand", new TestCommand());
     jcommander.addCommand("testAnotherCommand", new TestAnotherCommand());
     List<Candidate> completions = new ArrayList<>();
+    ParsedLine parsedLine =
+        new DefaultParser().parse(line, line.length(), Parser.ParseContext.COMPLETE);
     new JCommanderCompleter(jcommander)
-        .complete(
-            LineReaderBuilder.builder().build(),
-            new DefaultParser().parse(line, line.length()),
-            completions);
-    assertThat(completions).containsExactlyElementsIn(candidates);
+        .complete(LineReaderBuilder.builder().build(), parsedLine, completions);
+    List<String> actualValues = completions.stream().map(Candidate::value).toList();
+    List<String> expectedValues = candidates.stream().map(Candidate::value).toList();
+    assertThat(actualValues).containsExactlyElementsIn(expectedValues);
   }
 
   @Test