ARQ-1653 Add Thread propagation of Arquillian Contexts

The ExecutorService used in DroneInstanceCreator attempts to create
new Driver instances on a new Thread. The new Thread is missing the
Arquillian Contexts as they are bound to ThreadLocals. We need to
make sure the active Contexts used during the call to
DroneInstanceCreator is reactivated on the new Thread when creating
the Driver instance.

This addresses the Driver instance creation problem introduced by
Core 1.1.3.Final after reverting the Thread inheritance introduced
in 1.0.4.Final.
ARQ-1638 fixing chrome.binary capability propagation
ARQ-1634 Replacing tests with Unsafe to avoid instance construction
[maven-release-plugin] prepare release 1.2.4.Final
[maven-release-plugin] prepare for next development iteration
ARQ-1659 Updated Selenium to 2.40.0

* Removed AndroidDriver support
* Removed IPhoneDriver support
ARQ-1705 Updating Arquillian Core to 1.1.3.Final
[maven-release-plugin] prepare release 1.3.0.Final
[maven-release-plugin] prepare for next development iteration
ARQ-1700 Add injection points and support for multiple scopes
ARQ-1707 Adding DroneTimeoutException message
ARQ-1688 Dropped support for Selenium 1
ARQ-1708 Removed LegacyConfiguration
ARQ-1669 Removed temporary executor service workaround
ARQ-1700 Fixed Drone instance passed to destructor
ARQ-1742 Logging an error when injection fails
[maven-release-plugin] prepare release 2.0.0.Alpha1
[maven-release-plugin] prepare for next development iteration
ARQ-1745 Rename InjectionPoint to DronePoint.
ARQ-1747 Move InjectionPoint one level up in DroneContext.