Produce a warning for aar projects with apklib dependencies

This is a basic fix for an issue #337 with APK or AAR project having a dependency of AAR type, which in turn explicitly or implicitly depends on APKLIB artifact. When putting together the list of all transitive dependencies for current project, code looks up all AAR artifacts, and checks for any APKLIB dependencies for each of them. For each located "deprecated" dependency combination, a warning message is produced if corresponding Mojo parameter is set.

TODO: Think about a proper wording for both warning messages (first one for AAR project with APKLIB libraries, second one for any project with AAR dependencies, which explicitly refer to APKLIB libraries).

Random thoughts about the future:

1) What would happen to the JAR library in APK > AAR > APKLIB > JAR case, once we decide to start removing (ignoring) APKLIB dependencies for AAR projects? Should it be removed (i.e. not included in a list of transitive dependencies) as well?

2) For complex Android projects with dependency graph like "project > AAR > AAR > APKLIB", warning message is displayed twice. Once for each AAR artifact with APKLIB transitive dependency, although technically speaking it is the same error. IMHO this can be safely ignored - better be warned twice than get a broken Android app, right?
Should this warning also come up when it is an apk build where an apk depends on an aar that depends on an apklib. Imho yes.. does it do that already?