Update jline to 3.24.1

Due to dependency conflicts with the version of jline that SBT ships
with and broken ClassLoader created by SBT, we must fork any tests that
use jline. Fortunately, this is a small number of CLI debug related
tests. Because these tests must fork, they are moved to the
daffodil-test-integration project, where daffodil is staged for fork
execution and parallel test execution is disabled to reduce memory
usage. This causes a pretty large increase in execution time for
integration tests, but unfortunately there are not many good
alternatives.

This also adds a test that should fail if sbt or jline ever change to
fix this issue, allowing us to revert this change so integration tests
do not take as long.

This also found an issue in the CLI where if a bug is found we print the
stack trace to stdout instead of to whatever PrintStream the CLI is
configured to use for stdout. In most cases these are going to be the
same so doesn't matter, but in CLI testing that isn't the case.

daffodil-cli/src/main/scala/org/apache/daffodil/cli/Main.scala

@@ -1858,7 +1858,7 @@ class Main(
                       | to this bug.
                       |
                       |""".stripMargin)
-    e.printStackTrace
+    e.printStackTrace(STDERR)
     1
   }
 

daffodil-cli/src/test/scala/org/apache/daffodil/cli/cliTest/TestCLItdml.scala

@@ -123,18 +123,6 @@ class TestCLItdml {
     }(ExitCode.Success)
   }
 
-  @Test def test_CLI_Tdml_Debug_singleTest(): Unit = {
-    val tdml = path(
-      "daffodil-test/src/test/resources/org/apache/daffodil/section06/entities/Entities.tdml",
-    )
-
-    runCLI(args"-d test $tdml byte_entities_6_08") { cli =>
-      cli.expect("(debug)")
-      cli.sendLine("continue")
-      cli.expect("[Pass] byte_entities_6_08")
-    }(ExitCode.Success)
-  }
-
   @Test def test_CLI_Tdml_DebugFile_singleTest(): Unit = {
     val tdml = path(
       "daffodil-test/src/test/resources/org/apache/daffodil/section06/entities/Entities.tdml",