Android XML Views reference implementation + shared E2E matrix

[Alex Freas (akfreas)]

Adds a second Android reference implementation (legacy XML Views) alongside the existing Jetpack Compose one — both integrating the same SDK — and replaces the flaky UiAutomator E2E suite with a single Maestro flow set that drives both apps, mirroring the iOS SwiftUI/UIKit + shared-suite pattern.

What's in this PR

Reference implementations

• :views — new XML Views app (com.contentful.optimization.app.views) mirroring every Compose screen/component, with a setTestTag helper exposing the same kebab-case test ids.
• :shared — new library module hosting the platform-agnostic helpers (AppConfig, ContentfulFetcher, EventStore, MockPreviewContentfulClient, RichText) consumed by both apps.
• :compose — the former :app module, renamed.

SDK (packages/android)

• New com.contentful.optimization.views adapter (OptimizationManager, OptimizedEntryView, ScreenTracker, TrackingRecyclerView) — a thin wrapper over the same core API as the Compose adapter.
• Fix OptimizedEntry dropping a reset-variant re-resolution (its collector was keyed on preview-panel state instead of the entry).

E2E (Maestro)

• One Maestro flow set drives both apps via appId: ${APP_ID}, replacing the retired UiAutomator suite. The dwell/view-tracking contract stays in ViewTrackingControllerTest (JVM unit) + the iOS suite.
• Apps reach the host mock via the 10.0.2.2 emulator alias (no fragile adb reverse); flows reset via stopApp + a reset launch arg (no pm clear).
• Offline-behavior flows were removed — real airplane-mode toggling is nondeterministic on CI and the path is covered by the shared JS bridge's iOS tests. See maestro/OFFLINE_TESTING.md.

CI

• e2e-android-maestro runs on GitHub-hosted runners with a per-app emulator matrix, a cached AVD snapshot (warm boot), and the aosp_atd system image — not google_apis, whose Play Services and launcher ANR on the headless software-GPU emulator and overlay the app under test. Green on both apps.

Test-id contract

id: selectors match the node resource-id: Compose via testTagsAsResourceId = true, Views via a setTestTag extension that sets viewIdResourceName through an AccessibilityDelegateCompat (XML android:id can't hold kebab-case). SDK-side accessibilityIdentifiers surface as contentDescription, matched by Maestro's text selector. The same selectors resolve against both apps.

🤖 Generated with Claude Code

[wiz-inc-38d59fb8d7]

Wiz Scan Summary

Scanner	Findings
Vulnerabilities	-
Sensitive Data	-
Secrets	-
IaC Misconfigurations	1
SAST Findings	-
Software Management Findings	-
Total	1

View scan details in Wiz

To detect these findings earlier in the dev lifecycle, try using Wiz Code VS Code Extension.