kie-server: add tomcat8x and wildfly8x profiles + tweak cargo configuration

 * using jboss-deployment-structure.xml and disabling CDI as Wildfly 8.x
   tries to start the CDI service and instantiate beans that should be
   actually managed by Guice. As of now CDI is not required for Kie Server

 * added download.url property for each container so the default can be
   overriden and the container does not have to be downloaded every time
   from remote location

 * using cargo deafult location for downloads and installs as there
   is no need to use the custom ones (this was just leftover from
   copy-pasting the config)
I found that the behavior we are seeing in Wildfly 8.1.0 is actually a bug is CDI 1.1 and should be fixed in CDI 1.2. However, I am not sure when that will end-up in Wildfly. So basically in future, when we test with later versions of Wildfly (with CDI 1.2) this should not be an issue anymore. 

I could not find any container agnostic configuration option that would work on all containers, or at would not break deployment on the current containers.
Using the jboss-all.xml is not currently possibly as that breaks the EAP 6.3.x deployment. Not quite sure why.

I see few possible solutions right now:
1) Disable the CDI subsystem altogether using the jboss-deployment-structure.xml. Easy to do (in fact already done in this PR), but there might hit issues with other containers as @mswiderski described.

2) Create separate assembly for Wildfly 8.x that will include the jboss-all.xml file. The "standard" assembly for other containers would not include such file. This seems rather radical and it would probably require moving the integration into separate module (out of kie-server-services) as we would need the assemblies for the testing.

3) Drop the Wildfly 8.x from the test matrix. Not really a good idea as the Wildfly is currently the only pure "community" EE server from JBoss and I think we should make sure the KIE server runs well on it.

4) Somehow (e.g. XSLT or even copy the whole standalone.xml) configure the Wildfly 8.x before running the tests and set the configuration `require-bean-descriptor="true"` for entire container. Doable, but bit messy and may break once we update the Wildfly to newer version.

I am inclined to go with the 1), but I am very much open for further discussion.