fix: Device info activity crash on optimized build

[sameerasw]

This pull request standardizes the serialization and deserialization of data models throughout the codebase by adding @Keep and @SerializedName annotations to all relevant data classes and enums. These changes ensure that fields are preserved during code shrinking/obfuscation and that JSON keys are correctly mapped to Kotlin properties, improving reliability when working with Gson or similar serialization libraries.

Key changes include:

Serialization/Deserialization Enhancements:

• Added @SerializedName annotations to all fields in data classes and enums in the following files, ensuring explicit mapping between JSON keys and Kotlin properties:
  • DeviceSpecs.kt, Automation.kt, AppSelection.kt, DnsPreset.kt, LocationAlarm.kt, MapsChannel.kt, SnoozeChannel.kt, TrackedRepo.kt, UpdateInfo.kt, GitHubModels.kt, GitHubUser.kt [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11]
• Updated enums and nested data classes to use @SerializedName for each value, ensuring proper serialization of enum values (e.g., Automation.Type, Action.SoundModeType) [1] [2].

Obfuscation and Code Shrinking Safeguards:

• Added @Keep annotation to all major data classes, enums, and sealed interfaces to prevent their removal or renaming during code shrinking (ProGuard/R8), which is critical for reflection-based serialization/deserialization (All references above, especially [1] [2] [3].

Domain Model Consistency:

• Ensured all domain models related to device automation, GitHub integration, and user settings are now consistently annotated for serialization, reducing the risk of runtime errors and improving maintainability [1] [2] [3] [4].

Sealed Interface Updates:

• Applied @Keep and @SerializedName to sealed interface implementations (objects, data classes) for Action, State, and Trigger, making sure all automation logic components are serialization-safe [1] [2] [3] [4].

These changes collectively make the codebase more robust and ready for safe serialization/deserialization, especially in environments where code shrinking or obfuscation is enabled.