feat(groupChatManager): create a groupChat manager to create separate collections on a thread

[Jekrimo]

What this PR does 📖
create a groupChat manager to create separate collections on a thread, allow sending messages, listening to the collection for changes, eventEmitters for testing I presume

Which issue(s) this PR fixes 🔨

AP-660

Special notes for reviewers 🗒️
EDIT: Testable now. 3 Groups are hardcoded for testing. Users will show as unknown unless it's your user. There are also other bug's and features missing currently. Most have been identified in AP-732 -> AP-744

[phillsatellite]

Tested: I'm not 100% sure if its caused by the PR but can't seem to get past the Linking Satellites page when creating a new account. I switched back to Dev branch, created new account and got in fine, switched back to this branch and created new account and still got blocked at Linking Satellites

[stavares843]

/rebase

[stavares843]

tickets that jeff added

AP-732
AP-733
AP-734
AP-735
AP-736
AP-737
AP-738
AP-739
AP-740
AP-741
AP-742
AP-743
AP-744

thanks for adding @Jekrimo 🔨

[phillsatellite]

Tested: Only issues I've found that I don't think weren't already addressed was the error in terminal (switched to branch, yarn, yarn dev to get that error) and the other error in Console "Error: errors.textile.friend_not_found"

[Jekrimo]

Tested: Only issues I've found that I don't think weren't already addressed was the error in terminal (switched to branch, yarn, yarn dev to get that error) and the other error in Console "Error: errors.textile.friend_not_found"

I think this has to do with us tricking it currently to allow multi users. I say we leave it and open a bug for it. But Idk what everyone else thinks

[stavares843]

do we know why appears the errors.textile.friend_not_found from Phil's screenshot? I see that added here
https://github.com/Satellite-im/locales/blob/main/en-US.js#L469

can we fix the warning when it finishes compiling locally? atm we have zero compiling warnings after compiling

[netlify]

✔️ Yeeeehaw, deploy preview is ready!

🔨 Explore the source changes: fee27c5

🔍 Inspect the deploy log: https://app.netlify.com/sites/adoring-edison-dbcef8/deploys/6205176d3dd85a0008742882

😎 Browse the preview: https://deploy-preview-1291--adoring-edison-dbcef8.netlify.app

[stavares843]

is possible to get the textile error that phil mentioned above fixed as well? 🔨

[Jekrimo]

I'm tryin to recreate it and can't get the error, is it showing for anyone else?

[phillsatellite]

I'm tryin to recreate it and can't get the error, is it showing for anyone else?

Hey Jeff! Sorry didn't notice earlier I got that error from trying to react to a message, which you said above isnt working yet 👍

[stavares843]

thanks for testing @phillsatellite

[Jekrimo]

Awesome! That's great news, perfect!

[WanderingHogan]

what do you think about dumping the if/else and doing something like

        // Check if the message is a group or a direct message
        const messageType = RegExp(this.$Config.regex.uuidv4).test(
          this.recipient.textilePubkey,
        )
          ? 'sendGroupMessage'
          : 'sendTextMessage'

        this.$store.dispatch(`textile/${messageType}`, {
          to: this.recipient.textilePubkey,
          text: value,
        })
        ```

[WanderingHogan]

is this getting ready for something in the future, or leftover