chore(wildfly8): remove wildfly 8 modules and code

* Remove the WildFly 8 subsystem;
* Remove the WildFly 8 Maven modules;
* Adjust the engine-IT test README to only show WildFly profiles;
* Remove GlassFish Maven property.

Related to CAM-11106

README.md

@@ -91,12 +91,15 @@ This will build all the modules that make up the camunda BPM platform but will n
 
 ```
 distro/tomcat/distro/target (Apache Tomcat 7 Distribution)
-distro/jbossas7/distro/target (JBoss AS 7 Distribution)
+distro/wildfly/distro/target (WildFly AS Distribution)
 ```
 
 Running Integration Tests
 ----------
-The integration testsuites are located under `qa/`. There you'll find a folder named XX-runtime for each server runtime we support. These projects are responsible for taking a runtime container distribution (ie. Apache Tomcat, JBoss AS ...) and configuring it for integration testing. The actual integration tests are located in the `qa/integration-tests-engine` and `qa/integration-tests-webapps` modules.
+The integration testsuites are located under `qa/`. There you'll find a folder named XX-runtime for 
+each server runtime we support. These projects are responsible for taking a runtime container 
+distribution (ie. Apache Tomcat, WildFly AS ...) and configuring it for integration testing. The 
+actual integration tests are located in the `qa/integration-tests-engine` and `qa/integration-tests-webapps` modules.
  * *integration-tests-engine*: This module contains an extensive testsuite that test the integration of the process engine within a particular runtime container. For example, such tests will ensure that if you use the Job Executor Service inside a Java EE Container, you get a proper CDI request context spanning multiple EJB invocations or that EE resource injection works as expected. These integration tests are executed in-container, using [JBoss Arquillian](http:https://arquillian.org/).
  * *integration-tests-webapps*: This module tests the camunda BPM webapplications inside the runtime containers. These integration tests run inside a client / server setting: the webapplication is deployed to the runtime container, the runtime container is started and the tests running inside a client VM perform requests against the deployed applications.
 
@@ -105,24 +108,19 @@ In order to run the integration tests, first perform a full install build. Then
 We have different maven profiles for selecting
 * *Runtime containers & environments*: jboss, tomcat, wildfly
 * *The testsuite*: engine-integration, webapps-integration
-* *The database*: h2,h2-xa,db2,sqlserver,oracle,postgresql,postgresql-xa,mysql (Only h2 / postgresql is supported in engine-integration tests)
+* *The database*: h2,h2-xa,db2,sqlserver,oracle,postgresql,postgresql-xa,mysql (Only h2 and 
+ postgresql are supported in engine-integration tests)
 
 In order to configure the build, compose the profiles for runtime container, testsuite, database. Example:
 
 ```
-mvn clean install -Pengine-integration,jboss,h2
-```
-
-For using wildfly as the runtime container you have to additionally specify the wildfly version: wildfly8, wildfly10, wildfly11, wildfly12 or wildfly13. Example:
-
-```
-mvn clean install -Pengine-integration,wildfly,wildfly10,h2
+mvn clean install -Pengine-integration,wildfly,h2
 ```
 
 If you want to test against an XA database, just add the corresponding XA database profile to the mvn cmdline above. Example:
 
 ```
-mvn clean install -Pengine-integration,jboss,postgresql,postgresql-xa
+mvn clean install -Pengine-integration,wildfly,postgresql,postgresql-xa
 ```
 
 You can select multiple testsuites but only a single database and a single runtime container. This is valid:
@@ -131,9 +129,10 @@ You can select multiple testsuites but only a single database and a single runti
 mvn clean install -Pengine-integration,webapps-integration,tomcat,postgresql
 ```
 
-There is a special profile for JBoss Application Server:
+There is a special profile for the JBoss and WildFly Application Servers:
 
-* Domain mode: `mvn clean install -Pengine-integration,h2,jboss-domain`
+* JBoss Domain mode: `mvn clean install -Pengine-integration,h2,jboss-domain`
+* WildFly Domain mode: `mvn clean install -Pengine-integration,h2,wildfly-domain`
 
 Limiting the number of engine unit tests
 ----------