refactor(build): extract Android app into :client:androidApp (AGP 9)

[plusmobileapps]

Draft / stacked PR. Base is claude/vigorous-keller-24f315 (#312). Review/merge that first. Not yet verified on-device — see caveats below.

Why

AGP 9 removes compatibility between com.android.application and the Kotlin Multiplatform plugin. The shared :client:composeApp module applied both, producing:

The 'org.jetbrains.kotlin.multiplatform' plugin deprecated compatibility with Android Gradle plugin: 'com.android.application' … move the usage of 'com.android.application' into a separate subproject.

The other library modules already use com.android.kotlin.multiplatform.library (via the KMP convention plugin); only composeApp was still an com.android.application.

What changed

Module split

• New :client:androidApp module (com.android.application) holds the Android app: MyApplication, MainActivity, AndroidApplicationComponent (Metro DI graph), RootBloc helper, the launcher AndroidManifest.xml, res/, icons, signing config, applicationId, and versionName/versionCode. Depends on :client:composeApp.
• :client:composeApp is now a KMP Android library (com.android.kotlin.multiplatform.library) via the new androidLibrary { } DSL — unique namespace com.plusmobileapps.chefmate.composeapp, androidResources.enable = true, JVM 11. The actual class BugsnagInitializer stays here. Desktop (compose.desktop) and the iOS framework export are untouched.
• androidInstrumentedTest source set renamed to the new plugin's androidDeviceTest.
• Applied the AGP KMP library plugin by id (no version) on composeApp — AGP is already on the classpath via the app module, so an aliased version request fails the "plugin already on classpath" check.

Deployment / CI automation re-pointed at the new module

• build-release.yml: read version from androidApp, :client:androidApp:assembleRelease, APK under androidApp outputs.
• fastlane android lane: :client:androidApp:bundle + client/androidApp/build/outputs/bundle/release/androidApp-release.aab.
• bump-version.yml: writes versionName/versionCode to androidApp, keeps desktop packageVersion on composeApp, stages both.
• compose-ui-tests.yml: connectedDebugAndroidTest → connectedAndroidDeviceTest (renamed by the new plugin; instrumented tests dormant — see below).
• Docs + .agents/seed.md: installDebug / bundleRelease / assembleRelease and the version-field tables now point at :client:androidApp; desktop :client:composeApp:run unchanged.

Verified (via Gradle)

• ✅ :client:androidApp:assembleDebug — debug APK builds: manifest merges, resources/dexing/packaging succeed, and Metro DI graph resolves across the new module boundary.
• ✅ :client:composeApp:compileKotlinJvm — desktop/JVM still compiles.
• ✅ The KMP/com.android.application compatibility warning is gone.

⚠️ Not yet verified — needs local + device check

• On-device install/run and the instrumented robot UI tests. Under the new plugin, commonTest isn't yet routed into androidDeviceTest the way the old instrumentedTestVariant.sourceSetTree.set(test) did — both dependsOn(commonTest) and withDeviceTestBuilder { sourceSetTreeName = "test" } failed expect/actual resolution. The build is green (device-test compilation is NO-SOURCE), but the shared Android instrumented tests are currently dormant. See TODO(agp9) in client/composeApp/build.gradle.kts. Main remaining task; compose-ui-tests.yml's Android job will run no tests until it's resolved.
• assembleRelease / bundleRelease signing and the AAB artifact name (androidApp-release.aab, inferred from the debug APK name) weren't exercised end-to-end.

Out of scope

Pre-existing android.newDsl=false / android.builtInKotlin=false and Compose version-catalog deprecations remain (separate cleanup).

🤖 Generated with Claude Code