Create a parent pom or bom for dependency management

[bstansberry]

We're independently controlling dep versions in the various maven modules in this repo, and it's messy. For example we have 3 different version of WildFly declared in 7 different locations, all badly out of date:

$ git grep version.org.wildfly\> | grep -v \{
authentication/wildfly-mods/profile.xml:                <version.org.wildfly>27.0.0.Alpha4</version.org.wildfly>
authentication/wildfly/pom.xml:        <version.org.wildfly>27.0.0.Alpha4</version.org.wildfly>
concurrency/concurrency-tck-runner/pom.xml:        <version.org.wildfly>27.0.0.Alpha3</version.org.wildfly>
faces/wildfly/pom.xml:        <version.org.wildfly>27.0.0.Alpha4</version.org.wildfly>
security/wildfly-mods/profile.xml:                <version.org.wildfly>27.0.0.Alpha4</version.org.wildfly>
security/wildfly/pom.xml:        <version.org.wildfly>27.0.0.Alpha4</version.org.wildfly>
wf-core-tck-runner/pom.xml:        <version.org.wildfly>27.0.0.Beta1</version.org.wildfly>

A fix for this would likely require changes to the Jenkins jobs that run these (perhaps just adding -am to mvn commands) and would probably force an adjustment to the maven versions of the various modules themselves (which seems needed regardless as none of them use -SNAPSHOT).

[jamezp]

Should we use something like https://github.com/wildfly/wildfly-dev-tools/tree/main/parent-pom? My intention was not to do a release for every WildFly release, but we could. We could then just depend on the BOM and import that.

Or maybe for the BOM project, we create a org.wildfly.bom:wildfly-container-parent or something that is released. Then each POM in here can use that as the parent.

[bstansberry]

@jamezp Make https://github.com/wildfly/wildfly-dev-tools/tree/main/parent-pom the parent? That's fine for plugins but I don't think we want production code versions managed by that repo.

Something from the boms project could work, but the boms project is going away, moving into the main WF code.

[jamezp]

If the BOM project is moving back to WildFly we could just use that to ensure we get the correct components. We basically just need a BOM that will hold the version of WildFly we need. Maybe some other components too like the EJB client or things like that.