Make clear distinctions between DMs & Groups with common Conversation

[nplasterer]

With DMs being a group under the hood I'm afraid the lines between the two are going to get increasingly more confusing and potentially cause bugs. To make this easier I think we should make very clear distinctions between DMs and Groups with a common interface of Conversation when doing both in the bindings.

Here are some functions that should exist

• [ ] listGroups - (filters groups on NOT type dm)
• [ ] listDms - (filters groups on type dm)
• [ ] listConversations - (no filter aka dms and groups)
• [ ] streamGroups
• [ ] streamDms
• [ ] streamConversations
• [ ] findConversation(id) - (probably no longer need the findGroup method)
• [ ] consentType - (GROUP_ID, INBOX_ID, ADDRESS) should be -> (CONVERSATION_ID, INBOX_ID, ADDRESS)
• [ ] streamAllGroupMessages -> we need this in the dualsending interim when we don't want to stream dm groups
• [ ] streamAllMessages -> this will be used to stream all messages in a V3 only world

[richardhuaaa]

This sounds great to me. Do any of these involve breaking changes to the meaning of existing methods?

[nplasterer]

I don't think there is enough meaningful data in the local consent database to warrent a major issue with renaming GROUP_ID to CONVERSATION_ID but that would be the only breaking change.