Migrate SharedPreferences to DataStore

[kelvin-ngure]

Describe the feature request. Following this pull request. We will migrate all the functionality of unencrypted shared preferences to datastore.

Additional context

Acceptance criteria A check list of all things to verify once the implementation by the engineer is complete

Area path A list of ordered steps in the app on usage of the feature to support anyone testing it e.g. Code reviewer, QA e.g.

1. Login to the app
2. Open Navigation bar
3. Click on Children register
4. Click on Child profile
5. Click on Edit profile from menu

Implementation plan (For Engineers) Create serializable wrapper data classes for relevant SDK classes Replace shared preferences functionality Update view models with StateFlow when needed Write new tests Remove unused tests Update documentation

[kelvin-ngure]

@f-odhiambo @ndegwamartin The most significant items left are

• [x] 1. Creating a Serializable wrapper for LocationHierarchies to allow storage
• [x] 2. No longer write the whole practitioner details object to preferences and check if the practitioner details store is empty instead when fetching token in the login view model. This is because the whole object is only used for that purpose
• [ ] 3. There's a single read I need to port that seems to use REMOTE_SYNC_RESOURCES
• [ ] 4. Updating tests that need proto datastore
• [ ] 5. writing any new tests and docs