Enforce inter-package dependencies within Catalog UI Search

[Lambeaux]

Description

Normally in an OSGi environment, where a feature consists of many jars/bundles, going through the Maven project steps provides some degree of dependency protection. Culturally it also raises additional awareness and discipline because a project's larger-picture dependency graph directly impacts the potential for a clean build, parallel build, and an otherwise painless CI/CD experience.

For how classes are packaged within a Maven module, the impacts of a messy dependency graph are substantially less punishing, until the module needs to be split, or some other concern enters the picture.

Expected behavior:

Look into the current interpackage relationships within Catalog UI search, see what can easily be cleaned up, and then enforced at build time so the package dependencies stay clean.

Version

N/A until progress starts.

Additional Information

Impacts: #4656

Might be worth looking into the following:
https://www.archunit.org/
https://blog.jdriven.com/2018/10/testing-the-architecture-archunit-in-practice/
http://www.mojohaus.org/extra-enforcer-rules/banCircularDependencies.html

[Lambeaux]

Migrated to https://github.com/codice/ddf-ui/issues; closing.