Feature request: Allow to have one central configuration module

It would be good to specify one (or more) central configuration packages in the @Modulithic or @Modulith application.

@Modulithic(configModules = ["config"])

This module/s has/have access to all other modules and even to internal classes that are not public (classes that do not reside in the top level package of a module and also do not reside in a @NamedInterface-package)

Yes, I think this is against the thought of modularization, but the advantage of the Modulith against MicroServices is, that I can still have a centralized configuration for the whole application without creating too many NamedInterfaces that could also be accesses by other modules, even if they should not access it. Goal is to keep this beans / classes private (without @NamedInterface) but still be able to configure them via a central configuration.

Similar to open sharedModules, but the other way around.

Open for discussion. Thanks!

Start by reviewing how @Modulithic and @Modulith currently define sharedModules and module boundaries. Determine how central configuration packages would access private classes without exposing them through @NamedInterface, and define tests that verify the access rules and configuration behavior.