ClassNotFoundException (AlternativePropertyReplacingBeansXmlParser) during deploying of MP JWT deployment.

 Steps to reproduce

• build WF from main branch
• Use distribution from dist module
• Deploy the deployment from the reproducer from JBEAP-23365 jira
• You will see this exception:

  14:44:21,524 INFO  [org.jboss.as.weld.deployment.processors] (MSC service thread 1-1) Cannot find constructor for org.jboss.as.weld.deployment.AlternativePropertyReplacingBeansXmlParser: java.lang.ClassNotFoundException: org.jboss.as.weld.deployment.AlternativePropertyReplacingBeansXmlParser from [Module "org.jboss.as.weld" version 27.0.0.Beta1-SNAPSHOT from local module loader @4ebff610 (finder: local module finder @60410cd (roots: /home/mkopecky/playground/wf/wildfly-2022-03-11/modules,/home/mkopecky/playground/wf/wildfly-2022-03-11/modules/system/layers/base))]
  	at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:200)
  	at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:410)
  	at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
  	at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116)
  	at org.jboss.as.weld@27.0.0.Beta1-SNAPSHOT//org.jboss.as.weld.deployment.processors.BeansXmlParserFactory.<clinit>(BeansXmlParserFactory.java:43)
  	at org.jboss.as.weld@27.0.0.Beta1-SNAPSHOT//org.jboss.as.weld.deployment.processors.BeansXmlProcessor.deploy(BeansXmlProcessor.java:73)
  	at org.jboss.as.server@19.0.0.Beta5//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:182)
  	at org.jboss.msc@1.4.13.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
  	at org.jboss.msc@1.4.13.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
  	at org.jboss.msc@1.4.13.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
  	at org.jboss.threads@2.4.0.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
  	at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
  	at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
  	at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
  	at java.base/java.lang.Thread.run(Thread.java:829)
  

• If you do the same with the distribution from ee-9/dist module, exception is not thrown there

The situation about this exception needs to be clarified. This jira will be blocker if current dist module will be used as a base for new EAP XP5. If ee-9 will be used as a base for XP5, this jira don't needs to be a blocker.