Add get and write HealthData by UUID method

[agilst]

• Update README file
• Update example app to show health point detail on the bottom sheet dialog
• Adjust fetch data loading indicator sizing

Note: both Swift and Kotlin codes to getDataByUUID is copied from getData and modified to return an single record instead of list.

[agilst]

Based on this issue #1139, I have updated writeHealthData and writeWorkoutData to return HealthDataPoint instead, but keep the writeBloodOxygen and writeMenstruationFlow to return bool.

Kindly review and make additional changes if required. Please let me know if we need/have different approaches to achieve this goal.

[iarata]

Thanks for the PR! I was actually trying to make this after I saw #1139.
Wouldn't it make sense for the get method to not have start and end time? If one already knows the exact UUID of a record then I think it wouldn't make sense to filter to a specific range

[agilst]

The start and end time is for Android only as they do not expose any API to get a single record by uuid, so I'm using tiniest time range to get small amount of records then find it by uuid. however, start and end time will not be used for iOS as it only needs to pass uuid and type to get a single record.

[iarata]

In health connect there is two ways to read readRecord and readRecords.
Only the readRecords need a ReadRecordsRequest which requires a time range, otherwise the readRecord just needs the id and type:

suspend fun <T : Record> readRecord(recordType: KClass<T>, recordId: String): ReadRecordResponse<T>

[agilst]

oh my bad I wasn't aware of it. I can switch to that method instead

[iarata]

@agilst could you separate the implementation for android to a new PR? i have stopped adding new features to the swift due to #1175

[agilst]

@iarata I'm afraid I couldn't make any changes on this branch (on forked repo) as I'm using it for production. I will instead create a new branch for iOS and Android for this implementation and sync with master changes for me to work safely, then I will submit a PR for iOS first followed by Android afterwards.

Edit: I will also separate the write implementation so things don't get mixed up.

[agilst]

@agilst could you separate the implementation for android to a new PR? i have stopped adding new features to the swift due to #1175

iOS part is done here #1193. please review

[agilst]

@iarata Separated Android implementation PR is here #1194