Support custom path for AndroidManifest.xml and res folder

The maven-android-plugin enables the user to define custom paths for
AndroidManifest.xml and res folder. Our plugin did not take into account
these properties. This commit addresses the issue by reading the
parameters from the POM and linking the AndroidManifest.xml file and the
res folder to the custom paths.
Tests for custom AndroidManifest.xml and res folder path

This commit adds test to verify that in case of custom manifest and res
folder the files are linked in the project.
Corrected name in getConfiguredFile()

The method contained variables named with specific meaning (assets),
since this method is generalized, the variables should have generalized
names, too.
Merged test project assets and resources test projects

It is unnecessary to have three different projects for the custom
assets, res and AndroidManifest.xml cases, so these are tested now in
the same project.
Merge branch '168_customResourcesFolder' of
https://github.com/WonderCsabo/m2e-android into master

Conflicts:
	me.gladwell.eclipse.m2e.android/src/main/java/me/gladwell/eclipse/m2e/android/project/AdtEclipseAndroidProject.java
	me.gladwell.eclipse.m2e.android/src/main/java/me/gladwell/eclipse/m2e/android/project/JaywayMavenAndroidProject.java
Removed redundant method for matching projects to dependencies.
Fixed stalling continuous builds.

Travis continuous integration builds were stalling due to stale version
of Android SDK build tools.

Upgrading this dependency resolved the issue on the local Vagrant build.
See here for more information:

https://github.com/rgladwell/m2e-android/issues/215