WFLY-1840 Put Multi-JSF installer into WildFly build (take 2)

Here is a new PR for this.  This one does not create module.xml files with relative paths.  Instead, it copies the needed jars into the module.  See https://github.com/wildfly/wildfly/pull/4893/ for previous discussion.

This installer tool doesn't actually add anything to the WildFly server. It just creates a CLI Deployment Archive.

The reasons I want to move it into the build are:
1) The installer creates a CLI deployment archive customized to a particular WildFly version. Because of that, it has proven to be nearly impossible to maintain the tool outside the WildFly build.
2) My personal GitHub account is certainly not the right place for the tool.
3) With the tool living as part of the WildFly build, we now create a default CLI archive that is capable of installing the latest MyFaces version. The CLI archive will be automatically uploaded to Nexus where anyone can use it without having to run the tool.

See https://issues.jboss.org/browse/WFLY-1840 for more details.