fix(platform-android): disable persistent Android snapshots after an unhealthy helper retirement
Summary
After a persistent Android snapshot helper becomes unhealthy, subsequent snapshot requests can continue attempting the persistent path and encounter the same stalled-device failure instead of reliably using one-shot capture. A failed helper retirement can leave the release state unproven or cleanup timed out, indicating that the device may still be affected by the frozen helper. The lifecycle did not previously remember that device-specific condition, so later requests could retry persistent sessions.
Track unhealthy devices for the daemon runtime when forced retirement cannot prove release or cleanup times out. Skip persistent-session acquisition for those devices while preserving one-shot fallback, emit a diagnostic with the disable reason, and clear the state when sessions are reset. The retirement API now returns release and cleanup status so the caller can make this decision.
Fixes #3929
Test plan
The focused Android snapshot-helper lifecycle tests passed.
The repository lint check completed without reporting a failure.
The package validation script completed successfully.
Ran pnpm run test-app:install in a Linux container (localhost/osc-linux-node:22) for the agent-device acquireAndroidSnapshotHelperSession change; it passed.
The tests in packages/platform-android/src/__tests__/snapshot-helper-session-lifecycle.test.ts fail without the fix in the agent-device acquireAndroidSnapshotHelperSession change (checked by reverting the source changes).