Option 1. Test BOM

• Consider introducing a separate bom exclusively for the test dependency management
• Eventually it would contain only JUnit 5 deps, but could support JUnit 4 as well for the starters
• Could have a faster update cycle than the main third-party lib bom (even depend on later Java versions?)
•  dependency bot currently works on the boms & could work on test-boms with little adaptation
• Caveat: we'd have to import dep mgmt of the two boms now, not just one.
  To validate: what exact benefits this effort brings?

Option 2. Move test dependencies to parent

• let the parent pom provision dep management for tests
• simpler module setup
• a lot of hassle updating the libraries (would require parent pom release!?)

Also consider extracting out the so-called magnolia-integration-tests-framework (the one used for non UI tests) into its own module (could be a submodule of test-framework?) and manage dependencies there (as was done for UI test dependencies in MGNLTEST-200).