Detect android-maven-plugin with new groupId

The groupId of the plugin changed to com.simpligility.maven.plugins, so
we have to return the plugin if it uses the new groupId.
Add test for new android-maven-plugin groupId

This test verifies that a project using the new version of AMP can be
configured with m2e-android.
Updated instructions to avoid stalled builds.

Updated instructions to avoid stalled builds due to Google ADT update usage dialogue boxes.
Merge pull request #277 from WonderCsabo/275_supportNewAndroidMavenPluginGroupId

Support for new Android Maven Plug-in.
Fix ProjectImporter with default destination

If the destination directory is not set, the ProjectImporter will use
the artifact name as the project folder. But there was a problem with
calculating the destination in that case: relative path used instead of
absolute path.
Compatibility with android-maven-plugin-4

Since version 4.0.0 the android-maven-plugin uses the gradle / Android
Studio folder layout. This means AndroidManifest.xml is at
src/main/AndroidManifest.xml, res is at src/main/res and assets is at
src/main/assets by default. We already support non-ADT folder layout by
using Eclipse resource links to point to the actual resource. The only
thing this commit is changing that we are now reading default values
from the android-maven-plugin parameters, so we can link to the default
structure even if the user do not explicitely define these properties.

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