Add ability to opt in to service config data initialization

While converting to native images for solo memory reduction, we noticed that we need to provide reflection hints for all of the config classes in the `com.hedera.node.config.data` package because these classes are eagerly loaded. Mirror node operation doesn't utilize the majority of these config classes and having to register the hints adds unnecessary bloat to the native image. Is it possible to provide the ability to opt in to loading specific config classes necessary for application operation?

Start by tracing configuration initialization for the com.hedera.node.config.data package and how reflection hints are supplied for native images. Compare the classes required by mirror node operation with the eagerly loaded set; done means applications can opt in to only the config classes they need without adding unnecessary native-image hints.

Written by the indexing model from the issue text.