Receiving the TokenMaster token - added previously missed recipient scenarios

[benjthayer]

@jorge-campo discovered we were missing a couple of scenarios whereby the recipient of the TokenMaster token was either:

a) Not yet a member of the community the TM token is minted for b) Is a member of the community but has not yet shared the address that the TM token resides in with the community

Previously the designs assumed that the recipient was already a member of the community and had shared the receiving address with the community - which is still a valid scenario and remains part of the flows.

The new flows covering these 2 additional scenarios are here: https://www.figma.com/file/qHfFm7C9LwtXpfdbxssCK3/Kuba%E2%8E%9CDesktop---Communities?type=design&node-id=51847-233674&mode=design&t=fPldGgJ0l3P0queh-4

Summary of changes:

1. When the Owner goes to airdrop a TM token, a new dialog is shown - this explains what permissions the recipient will assume, clarifies that they will need to remotely destruct the token in order to revoke the permission and also advised them to ensure the recipient is a member of the community and has already shared the receiving address with the community. While this last part is not strictly necessary, it makes the assumption of the TM role by the recipient much quicker and more straightforward.

--

2. When the recipient receives the TM token, they receive a notification centre item with a CTA to learn more. This CTA launches a dialog (as shown in point 3 below).

--

3. The TokenMaster token dialog: When clicking on the notification centre item, the user will see a dialog which introduces them to the token and the permissions it avails to them. Based on the recipient's state, the copy of this dialog and it's primary CTA varies:

a) If the user is a member and has already shared the address holding the token with the community: The user is directed via the copy and CTA to the community admin section given, at this point, they have automatically assumed TokenMaster access to the community

b) If the user is a member but has not already shared the address holding the token with the community: The user is directed via the dialog copy and CTA to edit their shared addresses ensuring they share the address hodling the token

c) If the user is not yet a member of the community The user is directed via the dialog copy and CTA to join the community by sharing the address that hodls the token

[caybro]

CC @noeliaSD

[noeliaSD]

@alexandraB99 probably also for ui-team.