ARQ-655 Update to take advantage of the new ShrinkWrap BOMs

* ShrinkWrap 1.0.0
* ShrinkWrap Resolver 1.0.0-beta-6
* ShrinkWrap Descriptors 2.0.0-alpha-2
ARQ-852 Remove examples from Arquillian Core

Replaced by Arquillian-Showcase: https://github.com/arquillian/arquillian-showcase

No containers live in Arquillian Core anymore, having examples here cause a cyclic dependency between Core and the Containers.
ARQ-842 Add handling of defining unknown launch configuration activation
ARQ-840 Remove 1 minOccurs restruction to simplify switching between 1 set and default configuration

* Removed dependencies on container element, not supported in 1.0
ARQ-807 Add warning on unused configuration options to notify user of possible missconfiguration
ARQ-686 Removed arquillian-parent from arquillian-bom to avoid bom dependency on jboss-parent

 * Formatted poms
 * Removed uncommented tests classified dependencies
 * Removed URL from child pom packaged types
ARQ-853 Add JavaDoc to user facing APIs with code examples
ARQ-619 Add handling of exception case where multiple DeployableContainers found on classpath or problems creating the DeployableContainer instance
ARQ-618 Add handling of two different exception cases, no container found and no matching container found during DeploymentGenerator validation
ARQ-858 Add validation rule that disallow multiple archive @Deployment's with the same archive name to target the same Container
ARQ-632 Close the MBeanServerConnection's created by the JMX Protocol
ARQ-686 Add required developer section to Arquillian BOM
ARQ-860 prepare release 1.0.0.Final
ARQ-860 prepare for next development iteration
ARQ-846 Protect ExceptionProxy againts Non-Serializable origin
ARQ-793 Add arquillian-config-impl-base to standalone profile to activate configuration for extensions
ARQ-889 Upgrade ShrinkWrap, Resolver and Descriptor version to fix BOM scopes
ARQ-971 Allow AuxiliaryArchiveAppenders to return null Archives.

Envionmental state might suggest to a AuxiliaryArchiveAppender that it should not append it's Archive. The only way for it to cancel itself in the current SPI would be to return null. Expand the DeploymentGenerator to filter and exclude null Archives from further processing.
ARQ-974 prepare release 1.0.1.Final
ARQ-974 prepare for next development iteration