Improve projects with conflicting support library dependencies

This patch addresses an issue that occurs when an Android project and one of it's dependencies both depend on different versions of the support library.  At first glance, an exclusion seems to be a simple solution to this problem.

    <dependency>
        <groupId>android.support</groupId>
        <artifactId>compatibility-v4</artifactId>
        <version>11</version>
    </dependency>

    <dependency>
        <groupId>com.actionbarsherlock</groupId>
        <artifactId>actionbarsherlock</artifactId>
        <version>4.2.0</version>
        <type>apklib</type>
        <exclusions>
            <exclusion>
                <groupId>com.google.android</groupId>
                <artifactId>support-v4</artifactId>
            </exclusion>
        </exclusions>
    </dependency>

This isn't so, bad but larger projects have many dependencies that rely on the support libraries.  Additionally, this works for command line builds, but IntelliJ 12.0.3 is unable to build.  This has to do with the way it builds each module and it should be fixed in 12.1.

APKLib dependency with exclusion
http://youtrack.jetbrains.com/issue/IDEA-98114

This patch allows support-v4 and support-v13 to be installed inline with the existing Google artifacts.  This avoids the need for dependency exclusions and both the command line and IntelliJ 12 can build.

    <dependency>
        <groupId>com.google.android</groupId>
        <artifactId>support-v4</artifactId>
        <version>r11</version>
    </dependency>

    <dependency>
        <groupId>com.actionbarsherlock</groupId>
        <artifactId>actionbarsherlock</artifactId>
        <version>4.2.0</version>
        <type>apklib</type>
    </dependency>