fix: harden accessibility service lifecycle and add desync health check

[natakhot271]

Summary

• defer app initialization until the device is unlocked
• avoid touching credential-protected/shared prefs during locked boot or direct-boot startup
• resume initialization automatically on ACTION_USER_UNLOCKED
• keep the accessibility service lifecycle resilient and add a desync health check
• remove redundant manifest noise and harden Android receiver registration

Why

The root cause was a startup-time crash before unlock: Android refuses access to credential-encrypted/device-protected storage while the user is still locked. Reef was attempting to initialize prefs too early during app startup, which could crash the process and leave the accessibility setting enabled while the service was effectively dead. This patch defers startup until the user is unlocked and safely resumes once the device is ready.

We also keep the service-health hardening in place so stale or interrupted accessibility state is easier to detect and recover from.

Steps to reproduce the bug

1. Start with Reef 4.3.0 with Mindful Launch set up.
2. Phone dies
3. User does NOT unlock phone in the first 20 sec after the boot
4. See Reef crash from trying to launch before unlock. Reef pid missing, and Accessibility Service for Reef stays not bound, but binding and active.

I am running Shizuku and debugging though its aShell on my phone.

adb logcat -d | grep -iE "ReefApp|IllegalStateException|SharedPreferences|credential encrypted storage|user.*unlock"

pidof dev.pranav.reef

dumpsys accessibility | grep -E "Enabled services|Bound services" -A 2

Fixes: #101, #88

Notes

• editor diagnostics show no Kotlin/XML errors in the changed files
• full Gradle compilation could not be run in this environment because no local Java runtime is installed

[natakhot271]

Tested Mindful launch with a debug apk! It works after a reboot + wait 30 sec to unlock, and doesn't work in Reef 4.3.0.