Mode 2097- Updated 3.x to use the community BOM

Since there is no release of the community BOM yet, the version it currently depends on is the latest SNAPSHOT. This will have to be changed later on, when the BOM is aligned with the dependencies form EAP 6.3 and released.

This pull request contains fixes for the following issues (which have snowballed because of the changes in the POMs):
- MODE-2097 - changed all dependencies to use the BOM
- MODE-2168 - Added support for EAP 6.2
- MODE-2169 - Package javadocs into a ZIP
- MODE-2197 - Updrade POI to 3.10-FINAL
- MODE-2175 - Fix repository vendor URL

Because of the new versions & plugin versions that are being brought in, some of the most notable changes include:
- replacing deprecated APIs used in tests with newer APIs 
- re-writing the `ConnectorTestCase` from `modeshape-jca` because the newer Arquillian-IronJacamar deps don't correctly shutdown on Windows
- moving the JBoss thirdparty uploads repository (for the Fungal dependency) out of `modeshape-jca/pom.xml` and into the build `settings.xml`

Prerequisites for building `3.x` with this PR:
- make sure the install scripts (`bin/install-eap`) are run locally and you have a version of EAP 6.2.0.GA installed locally
- make sure either your local Maven `settings.xml` is updated to reflect both the 3rd party uploads change (see above) and the EAP 6.2 repository __OR__ use the `settings.xml` file from this codebase to build
- after upgrading the BOM to use `jboss-parent-11`, I got (only once though) _a very weird error from the JavaDoc plugin_ about a mismatch between the X509 certificate provided by the `http://maven.repository.redhat.com/techpreview/eap6/6.2.1/maven-repository` site and the actual hostname. The workaround for me was to specify `-Dmaven.wagon.http.ssl.insecure=true -Dmaven.wagon.http.ssl.allowall=true` to the Maven runtime OPTS.