Android: Test apk size reduction

[vaslabs]

For #5961

Implementation

• Add the outer AndroidAppModule in the compileModuleDeps instead of moduleDeps
• Fix some packaging mappings to use run resolved deps
• Fix the compile only classpath to pass the compileModuleDeps classpaths too
• By having instrumented tests inherit the androidDefaultProguardFileNames from the parent module, the android tests are working. It's not clear to me why, I found it due to some trial and error. To achieve this kind of inheritance without major rewiring I've moved the method to AndroidAppModule

Other fixes and cleanups

• Somehow androidtodo had a wrong namespace, maybe a find and replace mishap
• Removed an unnecessary dep from androidtodo test module

Outcome

This avoids packaging the main (app) module dependencies and source code into the test apk.

Result (Jetsnack)

Future work

I had some difficulties reaching this point and I think the 13MB reduction is very satisfiable at this stage. In the gradle's case, it appears some classes are erased by R8 but I haven't pinpointed exactly how it does it.

[vaslabs]

the included sample apps are passing but I get failures in jetsnack when running the tests

[vaslabs]

Managed to make it work

it's not in the <1MB level of gradle yet, but it's getting there.

[vaslabs]

need only to fix the Android Res so leaving this as a draft for now

[vaslabs]

More Tests

Ref: https://github.com/vaslabs-ltd/compose-samples-with-mill/tree/android-test-apk-opts

JetNews

JetLagged

[vaslabs]

I think overall it's an improvement on the build flow (some fixes to pick run deps for tests and some transitive dependencies on android resources) and reduces the android test apk by a lot (13-15MB reduction) in most of the cases.

Ready for review @lihaoyi @lefou