Disables Spring's built-in ServletContainerInitializer which uses WebApplicationInitializer SPI that is discovered via slow class-path scanning. Now directly, and only, call the SpringBootServletInitializer via our own ServletContainerInitializer instead.

Be mindful if, in the future, we rely on other WebApplicationInitializers that will now not be run.

@@ -0,0 +1,29 @@
+package se.su.dsv.scipro.api;

@@ -43,6 +43,7 @@ public class UserProfileServiceImpl extends AbstractServiceImpl<UserProfile, Lon
     }
 
     @Override
+    @jakarta.transaction.Transactional

@@ -0,0 +1,4 @@
+package se.su.dsv.scipro.war;

@@ -18,2 +30,4 @@
+import java.util.concurrent.Executors;
+import java.util.concurrent.ScheduledExecutorService;
 
 public abstract class GuiceTest {

@@ -0,0 +2,4 @@
+
+import jakarta.persistence.EntityManager;
+import jakarta.persistence.EntityManagerFactory;
+import jakarta.servlet.FilterChain;

@@ -0,0 +7,4 @@
+
+import static org.junit.jupiter.api.Assertions.assertEquals;
+
+public class UrkundSettingsRepositoryTest extends SpringTest {

@@ -0,0 +16,4 @@
+import static org.hamcrest.CoreMatchers.is;
+import static org.hamcrest.MatcherAssert.assertThat;
+
+public class UrkundSubmissionRepositoryTest extends SpringTest {

@@ -0,0 +13,4 @@
+public class ApiController {
+    private final UserService userService;
+
+    @Inject