raygun: Add/store internal and external logging

[dariusc93]

In the current implementation of raygun, it does not support any internal or external logging that can be stored within the conversation document (or be apart of it). This may be beneficial when it comes to group chats for seeing different events as well as having a form of comparable logs to determine the balance between the conversation documents.

Internal Logs

Internal logs will store events of the conversation at the lowest level. This will include data such as messages apart of the conversation (only the message id), when a message been edited/modified/deleted, reacted to, as well as when a member been added/removed, etc. This type of log may be used to compute a value to determine of the conversations are the same with each other, a head or behind (see notes below) to make sure the members are up to date upon their initial connection to the peer or third party and there is no duplication of data among peer based on the metadata.

External Logs

The external logs will be show a list of events at a higher level, similar to above but will less verbose information unrelated to the API. For direct messages, both members will have access to the function. In group chats, the information may be limited from the interface depending on the caller of the method (though for now, the current group implementations may have access the same data as the creator while on larger scale, this may be limited based on permissions of the user in that conversation).

Note:

• The internal log may used or be based on crdt.
• This may replace Refactor rg-ipfs queue #141