separate the wildfly build/repo

The wildfly build should be further decoupled from the Teiid build. Initially this could be as simple as removing the module references from the parent pom. We also need to update the wildfly logic poms to start referencing teiid artifacts via a distinct version (rather than project.version).

From there we can decide how to promote it into its own repository. As it doesn't seem likely that we'll invest in a mechanism to update teiid-wildly using some kind of teiid core overlay, we'll likely just do a teiid-wildfly release with every teiid release.