After merging camunda-bpm-assert and camunda-bpm-junit5 into the Camunda Platform monorepo, we want to make sure to use the assertJ version that is also used in the currently supported Spring Boot version.

Idea:

• use dependencyManagement tag to import the version for assertJ from the spring boot bom
• override any other dependency that we want to manage ourselves and that is also managed by Spring Boot

Hint:

• https://docs.camunda.org/manual/7.16/user-guide/testing/#assertions-version-compatibility
• When we support two Spring Boot versions at a time which use different assertJ versions we need to be able to build multiple releases for both assertJ versions.
• Also investigate if assertJ is really necessary for camunda-bpm-junit5