Add remaining health connect sensors

[dshokouhi]

This request will be used to track the remaining sensors we can add according to: https://developer.android.com/health-and-fitness/guides/health-connect/plan/data-types as I am sure we will get more requests and quite possibly more will be added in the library

• [x] Active calories burned (#4452)
• [ ] Basal body temperature (#4836)
• [x] Basal metabolic rate (#4803)
• [x] Blood glucose (#4785)
• [x] Blood pressure (#4803)
• [x] Body fat (#4785)
• [x] Body temperature (#4803)
• [ ] Body water mass (#4836)
• [x] Bone mass (#4803)
• [ ] Cervical Mucus (not sure how this will work based on the docs)
• [ ] Cycling pedaling cadence
• [x] Distance (#4785)
• [x] Elevation gained (#4785)
• [ ] Exercise session
• [x] Floors climbed (#4785)
• [x] Heart rate (#4784)
• [ ] Heart rate variability rmmsd (#4836)
• [x] Height (#4803)
• [ ] Hydration (should be aggregate based on data available in docs) (#4836)
• [ ] Intermenstrual bleeding
• [x] Lean body mass (#4803)
• [ ] Menstruation flow
• [ ] Menstruation period
• [ ] Nutrition (will require extra care as its probably lots of sensors in it of itself)
• [ ] Ovulation test
• [x] Oxygen saturation (#4803)
• [ ] Planned exercise
• [ ] Power
• [x] Respiratory rate (#4803)
• [ ] Resting heart rate (#4836)
• [ ] Sexual activity
• [ ] Skin temperature
• [x] Sleep session (duration) (#4785)
• [ ] Speed
• [ ] Steps cadence
• [x] Steps (#4785)
• [x] Total calories burned (#4452)
• [x] VO2 max (#4803)
• [x] Weight (#4452)
• [ ] Wheelchair pushes (probably a good candidate for aggregate based on data available in the docs)

[dshokouhi]

Several of these are in progress in: https://github.com/home-assistant/android/pull/4803

• Basal metabolic rate
• Blood pressure diastolic
• Blood pressure systolic
• Body temperature
• Bone mass
• Height
• Lean body mass
• Oxygen saturation
• Respiratory rate
• VO2 max

[dshokouhi]

Exercise session (and related metrics) will need to have discussion around how it works or if it makes sense to add as records will be delayed since the app does not get notified for it. The Wear OS activity state sensor is better fit IMO but only applies for those watches. If we do add it the state as type will require a force update so we can update back to back records of the same type. End time will be unique but may not display well in the frontend without some effort.

For cycle tracking might be best to hold off until we get a user request so we can discuss what data is best to add

skin temp requires extra consideration in how to report it, do we go by average or latest record?

remaining sensors should also be requested and discussed before we add them