Feature: Flexible Filtering for `ApplicationModules`

Problem

ApplicationModules.of(…) factory methods are restrictive. Specifically:

• Naming Collisions: A DescribedPredicate sharing a name with the class blocks the import.
• Lack of Composition: Cannot apply multiple ImportOption filters (e.g., excluding tests AND fixtures) while using predicates.

Proposed Solution

Introduce a Builder or expanded Varargs support to match ArchUnit’s ClassFileImporter flexibility:

// Option A: Builder Pattern
ApplicationModules modules = ApplicationModules.builder(MyApplication.class)
    .withImportOption(ImportOption.Predefined.DO_NOT_INCLUDE_TESTS)
    .withExclusion(DescribedPredicate.resideInAPackage("..internal.."))
    .build();

// Option B: Importer Injection
ClassFileImporter importer = new ClassFileImporter()
    .withImportOption(new DontIncludeTests());
ApplicationModules modules = ApplicationModules.of(MyApplication.class, importer);

Start by reviewing the ApplicationModules.of(…) factory methods and the ClassFileImporter entry point described in the issue. Compare the builder and importer-injection options, then define an API that supports multiple ImportOption filters and exclusions without naming collisions. Done means callers can compose those filters while creating ApplicationModules.