Support additional data storage for paired devices

[Supereg]

Problem

Some paired devices might want to store additional metadata with their device. E.g., persist the last sequence number for a given user or persist the last known user data, user database number, consent code, etc ... from the User Data Service.

Solution

We should investigate (once we implement those features) how to best support these use cases. Either it makes sense to recommend users to store their device specific data on their own (maybe we can give recommendations on how to do the best?) or provide a mechanism to store these datapoints alongside the PairedDeviceInfo model.

Additional context

This will be relevant for the existing Omron devices of SpeziOmron. A specific instantiation of device specific metadata will reside in that target (storing the last sequence number and user information).

Code of Conduct

• I agree to follow this project's Code of Conduct and Contributing Guidelines