What a Quarkus application tells the runtime, and nothing more: credentials are
MicroProfile Config properties under nucleo.credentials.*, the nucleo.* properties bind
onto the registered Settings classes at startup, and the dispatcher's lifecycle rides
the CDI container's. The analog of nucleo-spring-boot-starter for the other host, built
on quarkus-arc and MicroProfile Config alone - no web framework, so it serves a REST
app or a batch process the same ...
