Following up to JBEAP-26889, where this log message was added to identify the server installation with EAP XP installed:

JBEAPXP0003: Starting container with JBoss EAP expansion pack installed.

However, the log message is present only when server configuration loads `modules/system/layers/microprofile/org/jboss/eap/expansion/pack/main` module.

This means one of these extensions needs to be active:

modules/system/layers/microprofile/org/wildfly/extension/microprofile/openapi-smallrye/main/module.xml
modules/system/layers/microprofile/org/wildfly/extension/microprofile/fault-tolerance-smallrye/main/module.xml
modules/system/layers/microprofile/org/wildfly/extension/microprofile/jwt-smallrye/main/module.xml

This isn't true for all server configurations, at least standalone-load-balancer.xml is not loading any of this so the log message is missing or any customized config without those extensions activated.
Domain mode is not supported for XP4 so I assume the same will apply for XP5, thus we can ignore domain configs.

I think it would make more sense to load it every time we have XP installed, regardless which config/extensions are activated.