[DRAFT] Shaded jar handling

[jfdenise]

For testing purpose.
Relies on a released SNAPSHOT of galleon-plugins: https://repository.jboss.org/nexus/content/repositories/snapshots/org/wildfly/galleon-plugins/wildfly-galleon-plugins/7.1.3.Final-SNAPSHOT/

[wildfly-ci]

Core -> Full Integration Build 14205 outcome was FAILURE using a merge of 6e6af87
Summary: Exit code 1 (Step: Build full with JDK 17 (Maven)) Build time: 00:06:18

[wildfly-ci]

Core -> Full Integration Build 13907 outcome was FAILURE using a merge of 6e6af87
Summary: Exit code 1 (Step: Build full with JDK 17 (Maven)) Build time: 00:04:49

[wildfly-ci]

Core -> WildFly Preview Integration Build 13984 outcome was FAILURE using a merge of 6e6af87
Summary: Exit code 1 (Step: Build & test full (Maven)) Build time: 00:06:12

[jfdenise]

The integration tests are expected to fail. We would need to synchronize changes in WildFly that are required: wildfly/wildfly@main...jfdenise:wildfly:shaded-jar-wildfly

A custom integration (with core and full updated) CI job show that tests are passing : https://ci.wildfly.org/buildConfiguration/WF_WildFlyCoreIntegrationExperiments/457864 (The test failures are due to the wildfly-galleon-plugins being a SNAPSHOT (glow maven config has snapshot disabled). Local tests are passing).

@bstansberry , the wildfly-cli:client shaded jar is built as before, it is just not used when provisioning it in the WildFly installation. It is still referenced in the bom:

The wildfly-elytron-tool-wrapper.jar is still built but is no more a shaded jar. It only contains the classes it defines. The shaded jar is built at provisioning time.

[jfdenise]

This is superseded by #6213