Sending a CentOps message from one participant to another

[turnerrainer]

This is a sub-issue of an epic #11

AS AN Architect I WANT all Bürokratt's participants to be able to communicate on a machine-to-machine level to exchange relevant technical information SO THAT all the relevant changes affecting the work of the Bürokratt Network would be applied ASAP

Acceptance Criteria

• [ ] An overview of sent messages and their statuses
• [ ] The actual content of the message must be encrypted by using an appropriate REST service
• [ ] Mock DMR endpoint

DSL

• [x] #114
• [x] #115

[baha-a]

@1AhmedYasser, Message structure:

[ 
    {
        "id" : 1,
        "message" : "hello",
        "status" : "SENT",
        "type" : "TEXT",
        "timestamp" : "2023-06-27T06:00:00.959+00:00",
        "replyToMessageId" : null,
        "senderId" : 123,
        "sender" : "Demo1",
        "receiverId" : 223,
        "receiver" : "Demo2"
    },
    {
        "id" : 2,
        "message" : "how are you?",
        "status" : "RECEIVED",
        "type" : "TEXT",
        "timestamp" : "2023-06-27T06:01:00.308+00:00",
        "replyToMessageId" : null,
        "senderId" : 123,
        "sender" : "Demo1",
        "receiverId" : 223,
        "receiver" : "Demo2"
    },
    {
        "id" : 3,
        "message" : "Great, thanks",
        "status" : "SENT",
        "type" : "TEXT",
        "timestamp" : "2023-06-27T06:02:00.308+00:00",
        "replyToMessageId" : 2,
        "senderId" : 223,
        "sender" : "Demo2",
        "receiverId" : 123,
        "receiver" : "Demo1"
    }
]

[turnerrainer]

@baha-a @baha-a when replying to a message, use REPLIED instead of SENT.

Well have a lot of situation where there will only beSENTandRECEIVED`, but in case of replying to messages, I want to clearly separate and find them fast.