jams-server: fix ssl error after initial setup

Modifications to the keystore.jks file are not taken into account by the jvm until jams is restarted once after setup. The issue turned out to be an underlying tomcat bug that is now resolved by bumping its version.

https: //redmine.savoirfairelinux.com/users/329
Change-Id: I4408d89e4241afb9a7a179ea3d7e415f6a575a2e

pom.xml

@@ -37,7 +37,7 @@
         <mockito.version>5.11.0</mockito.version>
         <mockito-inline.version>5.2.0</mockito-inline.version>
         <byte-buddy.version>1.14.12</byte-buddy.version>
-        <tomcat.version>10.1.19</tomcat.version>
+        <tomcat.version>10.1.24</tomcat.version>
         <map.struct.version>1.3.0.Final</map.struct.version>
         <maven.surefire.version>3.2.5</maven.surefire.version>
         <gson.version>2.10.1</gson.version>
@@ -76,6 +76,11 @@
             <artifactId>slf4j-simple</artifactId>
             <version>${log4j.version}</version>
         </dependency>
+        <dependency>
+            <groupId>org.slf4j</groupId>
+            <artifactId>slf4j-api</artifactId>
+            <version>${log4j.version}</version>
+        </dependency>
         <dependency>
             <groupId>com.google.code.gson</groupId>
             <artifactId>gson</artifactId>