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)
what I meant is disabling cdi completely might hide issues you will run into on regular containers. This particular case is not perfect example to illustrate this. Imagine another cdi thingy that will fail on fully enabled container (non jboss so the deployment file will be ignored). So my point was that lie-server should run on cdi enabled application server without disabling it even though it's not cdi based implementation. 
Because of that I thought that ensuring that a jar is real bean archive is better than disabling cdi completely. Does this make any sense to you?