Deep integration between ScienceMesh contacts to EFSS contacts

[michielbdejong]

In email, @david-antos suggested:

it also needs to keep track of sent invites and links to whom the invite was sent. Originally, I expected that when generating an invite, you either have a form to fill in mail of the other person (and the system keeps the relation of the mail for you). Or at least you have a field to fill in a name, should you send the invite by any other means. And again, you can then see a list of contacts in a familiar form and you can manage them.

I think if we are going to deal with email addresses and display names in the EFSS GUI then we should link that functionality to the existing EFSS addressbook functionality, instead of administering ScienceMesh contacts separately.

So translating this into tasks, I would say:

• [ ] add an invites manager in the Nextcloud/OC-10 backend (we are still using Reva's built-in JSON-based one), so when an invite is generated (whether through reva-cli or through efss-gui), it is stored in an invites table on the efss database (so we get "backdoor" access to this)
• [ ] in the 'generate new token' efss-gui (see nc screenshots and oc-10 screenshots, offer the option to link an address from the user's addressbook (create a new contact if needed), including email address and/or a displayname
• [ ] consider making this link obligatory
• [ ] if an email address or other contact method is available, and a mail relay or equivalent is available, send the invite directly instead of instructing the user to cut and paste the invite URL
• [ ] in the call to Reva include the contact ID
• [ ] in the Reva endpoint, include the incoming contact ID into the opaque data of the GenerateInviteTokenRequest that gets created
• [ ] in the invites backend, store it in the DB
• [ ] display it when listing sent invites
• [ ] consider using one database table for both pending and accepted invites, so the link to addressbook stays in tact after an invite is accepted

[michielbdejong]

See also https://github.com/cs3org/cs3apis/pull/197 so we can use the user's profile information for sending display name and email address, and also automatically (offer to) add ScienceMesh to a user's addressbook with the values that get provided via ScienceMesh.