ArchUnit 1.x is pulling in slf4j 2.x

[shakuzen]

We were inadvertently ending up with slf4j 2 on the classpath in places that also have an archunit dependency. ArchUnit upgraded to slf4j 2 in its 1.0 release, but we didn't notice because our wiremock dependency was shadowing slf4j 1.x without changing the package and it was ending up getting loaded by the classloader rather than the slf4j jar. The shadowing in wiremock was changed to use a different package, which is what uncovered the slf4j dependency getting managed to 2.x through archunit.

See #4776
See #3414