Update JarLauncher path after Springboot 3.2 update

[DropSnorz]

As spotted while preparing OwlPlug 1.25 release, the spring-boot-loader-tools 3.2 has been incorrectly picked during build because the version of spring-boot-maven-plugin was not pinned (43fce91)

In spring boot 3.2, loader classes in the org.springframework.boot.loader package has been relocated to org.springframework.boot.loader.launch.

References in pom.xml and packaging script must be updated.

This problem is not visible during development because JarLauncher is used by app binaries after the packaging step. The app fails silently on windows but we have following error message on linux.

java.lang.ClassNotFoundException: org.springframework.boot.loader.JarLauncher

[DropSnorz]

While updating from spring-boot 3.1.2 to 3.2.2, major performance degradation on database insert queries appears.

Seems a problem on h2 runtime somewhere between 2.1.214 and 2.2.224