Increased VM CPUs and memory to replicate Travis.

Increased virtual machine memory and CPUs to bring them in-line with
Travis images.

This also drastically increases the performance of tests running on the
Vagrant image.
Increased test speed by disabling redundant init.

Increased the speed of the integration tests by disabling redundant m2e
initialisation.
Fix: redundant dep causes build instability.

Removed redundant dependency causing build instability. This also
increases the speed of builds.
Test against latest m2e for pre-Luna releases.

Upgraded tests for pre-Luna Eclipse release (Indigo, Juno and Kepler)
to run against latest version of the 1.4.x m2e plugin.
Display stack traces during continuous build.
Hardcode platform provided dependencies

We remove the dependencies (and transitive dependencies) of the Android
artifact from the Maven classpath container, since the Android library
entry already contains these classes. Currently we do with this
dynamically with Aether, resolving all the dependencies and removing
them. Unfortunately we have problems with Aether. This commit replaces
resolution with Aether by simply returning the hardcoded dependency
lists for the artifacts.

https://github.com/rgladwell/m2e-android/issues/259
Fix: update site deployment failing.

https://github.com/rgladwell/m2e-android/issues/284
Merge pull request #263 from WonderCsabo/239_hardcodeAndroidDependencies

Hardcode platform provided dependencies.
Add test launch configuration after full project import

m2e-android only can configure the launch configuration correctly after
the project is fully imported. Unfortunetaly if a test project contains
a .launch file, it is configured because the project is fully
configured, so our launch configuration listener cannot modify the
launch configuration correctly. Since this commit, the launch
configuration file is not present at the project import, it is only
created after the project is fully imported.

This way we can reenable
"testConfigureAddsAndroidTestClasspathProviderToTestRunner" testcase.
Also the now we can successfully run a test project which actually tests
a class from the application, nut just uses the test class itself. This
was not possible before, because our test classpathprovider was not
added to the launch configuration at project import.
Modify testTestRunner testcase to demonstrate 221