Investigate using the ArchUnit module APIs in favor of the slice ones

[odrotbohm]

trafficstars

ArchUnit released a new module architecture rule API that seems inspired by the conventions of Spring Modulith. We should investigate in how far it allows us to port some of the concepts and verifications we built on top of ArchUnit can be replaced by using that API.

From a quick glance, it seems it supports:

• Modules by identified package (either naming pattern or annotations)
• Dedicated module APIs

It currently seems to lack explicit API to replace our named interfaces abstractions, in particular the ability to define dependencies to a named API.