Remove calls to status-go when handling a community

[cammellos]

Description

status-mobile/src/status_im/contexts/communities/events.cljs

Line 34 in 58e9ae0

:fx [[:dispatch [:communities/initialize-permission-addresses id]]

This code is run every time status-go signals the client of a community.

You can see that it will ask back status-go for extra information:

                              :fx [[:dispatch [:communities/initialize-permission-addresses id]]
            (when (not joined)
              [:dispatch [:chat.ui/spectate-community id]])
            (when (nil? token-permissions-check)
              [:dispatch [:communities/check-permissions-to-join-community id]])
            (when (some has-channel-perm? token-permissions)
              [:dispatch [:communities/check-all-community-channels-permissions id]])
            (when joined
              [:dispatch [:communities/get-revealed-accounts id]])]})))

This is generally a pattern we want to avoid, as in most cases, if there's any action to be performed, status-go should take care of that before passing it to the client.
Another issue is that it might create cycles, as this is called in response to RPC, but makes RPC calls, in this case it's handled by checking whether spectated/spectating is set, but it's fragile.

To start with, I think we should focus on removing spectating from a reaction to a status-go signal.
We should spectate a community only when we open a page of a community, not in response to any not-joined community in status-go.

Secondly, we should remove all the permisions checks. We should make those only when a user opens a community page.
And maybe we can discuss how to keep that page up to date, whether periodically, or by only checking permissions for that community that the user is on.

[ilmotta]

Closing as this tech debt is resolved. We now initialize permission addresses from a use-mount from the account selection component.