Add user storage usage to user-devices API

[mrjones-plip]

Is your feature request related to a problem? Please describe.
CHWs can run out of disk space and not know why their device is not performing as expected. Giving administrators an easy way to monitor this would be really helpful

Describe the solution you'd like
Right now there's a user-devices API which has per user information, but does not include used and total storage space on the device. If we add this to this report, it would make an easy way to find this data!

Describe alternatives you've considered
Administrators could either manually check telemetry documents per user in Couch (see deviceInfo.storage.free) or they could set up a process like CHT Sync or couch2pg to sync this data to a Postgres database.

These are either slow (manually checking) or hard to set up (syncing data), where as the API is built in.

Additional context

• Forum discussion.
• Original work on user-devices API

Good first issue

This ticket has the Good first issue label! This means it's been especially curated other CHT contributors to be easy to work on for first time contributors.

To succeed on this ticket, please:

1. set up your development environment - and ensure it works by logging in to you CHT instance
2. create an offline user called test in the administrative interface
3. log in as this user to ensure a unique device ID in the CHT is created
4. go to fauxton and create a document based on the JSON below
5. do a curl call to the user-devices API and not it's output: http://medic:password@localhost:5988/api/v2/export/user-devices - ensure you see the values from the document you created above
6. review the code changes made when the original User Devices API was added:
   • while 35 files were edited (a lot!) - check out the changes to api/src/services/export/user-devices.js and ddocs/users-meta-db/users-meta/views/device_by_user/map.js
   • how might you extend these two files to include two new values based on the earlier work in this PR?
   • look at the path in the JSON below - what will be the path you'll need to use to add the values to map.js?

Sample telemetry JSON

{
  "_id": "f9f8846e894b412e0ac45874d3005b01",
  "_rev": "7-76f4d0a2b4ab01fd37acfdea84fab57c",
  "type": "telemetry",
  "metrics": {},
  "device": {
    "userAgent": "Mozilla/5.0 (Linux; Android 10; TECNO KC8 Build/QP1A.190711.020; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/128.0.6613.146 Mobile Safari/537.36 org.medicmobile.webapp.mobile.moh_togo_echis/v1.1.0-alpha.echis_togo",
    "deviceInfo": {
      "app": {
        "version": "v1.1.0-alpha.echis_togo",
        "packageName": "org.medicmobile.webapp.mobile.moh_togo_echis",
        "versionCode": 101009900
      },
      "software": {
        "androidVersion": "10",
        "osApiLevel": 29,
        "osVersion": "4.9.190+(LMN-OP-201103V104)"
      },
      "hardware": {
        "device": "TECNO-KC8",
        "model": "TECNO KC8",
        "manufacturer": "TECNO",
        "hardware": "mt6761",
        "cpuInfo": {
          "cores": 4,
          "arch": "armv7l",
          "model name": "ARMv7 Processor rev 4 (v7l)"
        }
      },
      "storage": {
        "free": 16713310208,
        "total": 26544680960
      },
      "ram": {
        "free": 490688512,
        "total": 1919627264,
        "threshold": 150994944
      },
      "network": {}
    }
  },
  "metadata": {
    "year": 2024,
    "month": 10,
    "day": 12,
    "aggregate_date": "2024-10-13T09:42:59.143Z",
    "user": "test",
    "deviceId": "3ea7d1c5-3481-45a9-8989-728e95efda42",
    "versions": {
      "app": "4.9.2",
      "forms": {
        "abandonment": "7-df0764a3f37db1a1a673c3933ef7903f"
      },
      "settings": "6-d9a3d151837a45fde187d21206aa78a7"
    }
  },
  "dbInfo": {
    "doc_count": 572,
    "update_seq": 1252,
    "idb_attachment_format": "binary",
    "db_name": "medic-user-test",
    "auto_compaction": true,
    "adapter": "idb"
  },
  "quux": "banana"
}

[mrjones-plip]

@andrablaj - in a call with @jkuester earlier today we agreed that this ticket, while satisfying to work on for me, would be PERFECT for a new comer to the CHT. I'm going to work on it a bit to add a section for the "Good first issue" label

I've updated the labels , assignee and such accordingly!

[najuna-brian]

Hello @mrjones-plip , @andrablaj I would like to be assigned this issue
Thank you

[mrjones-plip]

Wonderful - thanks for your help @najuna-brian ! If you have any questions feel free to ask here or on the forums.

[andrablaj]

Thanks @najuna-brian! Additionally, please review the development workflow and the style guide for extra guidance about contributing to the CHT Core.

[najuna-brian]

Alright please. Thank you