DIDComm queued messages metadata #2300
Description
From #2292:
should we add some extra metadata to the queued messgages? So like a state (awaiting confirmation, or the date/time since we are awaiting confirmation) or do we see this more as a repository specific thing to have?
At the moment, implementations for both postgres and dynamoDB have shown that some state is required. But we need to define some common parameters that would be useful for different backends.