Make module glue class private when no config is required

For a scenario where the configuration is not needed, we could make the generated glue class private to decrease its IDE visibility. This would require making the methods/fields additionally accessible via reflection.

Start by locating the annotation processor or module-provider path that generates the glue class, then compare scenarios where configuration is required versus unnecessary. Determine how making the generated class private affects reflective access to its methods and fields. Done means the no-configuration case has reduced IDE visibility without breaking reflection.

Written by the indexing model from the issue text.