BOMs refactoring

Please DON'T MERGE THIS YET. It is still work in progress, but I want to get early feedback from others, so that's why I am creating this PR.

We discussed some of the changes with @ge0ffrey @rafabene and @pmuir in past few weeks. With @ge0ffrey  we decided _not_ to move the BOMs to community repositories as they should only be released when product is actually released. We will still create a CI job that will locally build the BOMs and quickstarts and will sure they work as expected.

The following changes should be done as part of the refactor:
* introducing `brms-bmpsuite-bom-parent` that will contain the shared info like version properties, etc
* added `jboss-brms-bpmsuite-bom` that contains only the drools/jbpm/optaplanner artifacts (no javaee stuff)
* refactored the `jboss-javaee-6.0-with-drools` into `jboss-javaee-6.0-with-brms-bpmsuite` as it already listed more than just Drools artifacts.


Yes, all of the above is definitely true. However, these product specific BOMs and Quickstarts and a bit special. If we add the JBoss.org repo into the POM, this will only work with community SNAPSHOTs. Once we would need to do a product build (with -redhat versions) then we need to specify additional repo where those artifacts are (they are not in the JBoss.org repo). This can be solved by another product specific settings.xml.

The ultimate goal is I think the ease use, so agree that adding the JBoss.org repo directly into the POM is much easier for developers. I will do that. For the product build, we will need to have additional settings.xml with that product repo specified.