Now that WildFly version 27 no longer supports Java 1.8 we need to either drop support for Java 1.8 or we need to test against WildFly 26.1 (the last one to support 1.8) when a CI build is using Java 1.8.

Since we are not quite ready to drop Java 1.8 support this issue will update the CI scripts to use WildFly 26.1 when the JDK version is less than 11 and to use WildFly latest otherwise.

Some axes (XTS, RTS etc) build our own jboss-as 5_BRANCH and these axes can only run on JDK 11 or above.

Also note that WildFly uses the maven-enforcer-plugin to verify that the Java is in the range [11,12) which equates to any version of Java 11 so, for example, we won't be able to use the WildFly main branch with Java 17