Fix for EAR Deployment Issue

[onuridrisoglu]

Description

DeltaSpike's JMX MBeanExtension observes BeforeBeanDiscovery and, during that callback, resolves the DeltaSpike ProjectStage via ConfigResolver.getConfigProvider(). That method discovers its ConfigProvider implementation using ServiceLoader against the thread context classloader (TCCL).

When this add-on's WAR is nested inside an EAR on a Jakarta EE server (e.g. WildFly / JBoss EAP 8), the TCCL active during CDI bootstrap is the EAR (parent) classloader, which cannot see deltaspike-core-impl in the WAR's WEB-INF/lib. The lookup finds no provider and deployment fails with:
java.lang.RuntimeException: Could not load ConfigProvider

This PR adds a new CDI extension, DeltaSpikeConfigBootstrap, that primes and caches the DeltaSpike ConfigProvider early — while the TCCL is temporarily set to the WAR module classloader (which can see WEB-INF/lib). ConfigResolver caches the provider in a static field, so DeltaSpike's later lookup returns the cached instance and never re-runs the failing ServiceLoader scan. The priming is best-effort (failures are logged at FINE and fall back to the normal path), and is a negligible no-op cost for standalone WAR deployments where the problem doesn't occur.

Fixes #521

Type of change

• Bugfix
• Feature

Checklist

• I have read the contribution guide: https://vaadin.com/docs/latest/guide/contributing/overview/
• I have added a description following the guideline.
• The issue is created in the corresponding repository and I have referenced it.
• I have added tests to ensure my change is effective and works as intended.
• New and existing tests are passing locally with my change.
• I have performed self-review and corrected misspellings.

[cla-assistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[TatuLund]

There are test failures that needs to be checked before merging.

[TatuLund]

There are test failures that needs to be checked before merging.

This was a setup issue.