Stop relying on the root pom for dependencyManagment. Use bom poms for the dependency sets used for different WF flavors and have other modules import the relevant dependency set. For cases where the correct dependency set for a module depends on what profile is used (i.e. testsuites), have the artifactId of the imported bom controlled by a maven property and use the profiles to choose the right property value.

Goals

1) Make it easier to build and test alternative versions of WF (e.g. WF Preview).

2) Let us move faster on converting standard WF to jakarta.* by making it easier to swap the dependencies used by one of our maven modules.

3) Make progress on clarifying the bill of materials used to build and test WF. Some projects use our root pom as a bom, and it's not designed for that purpose. I don't think any of the poms in the wildfly/wildfly repo are meant to be used as a bom, but I expect people will do so anyway, so we're better off having more formalized dependency management. It will help our own work in the long run too, I think.

See https://lists.jboss.org/archives/list/wildfly-dev@lists.jboss.org/thread/A2ULGAF2VGAONJ272L6N5I44QVVPSYLH/ and https://wildfly.zulipchat.com/#narrow/stream/174184-wildfly-developers/topic/Build.20boms for further discussion.