Kotlin dependencies are used by some of our modules (e.g. external-dams) or pulled in transitively by other 3rd party dependencies. This may cause issues with conflicting versions ending up in Magnolia webapps, like the incident with a recent webp-imageio update (depending on Kotlin 1.9.x) which stopped working on some customers' setups due to an older, incompatible Kotlin version in the classpath pulled in by some Magnolia module.

Let's manage Kotlin in bom so to have a predictable version in all Magnolia's webapps.