include names in `to/cc/bcc` fields when calling FES

[tomholub]

I don't think the change I've done will work @tomholub

Browser-extension is stripping out the names of the Google contacts - and sending just the email address.

{"associateReplyToken":"e24d308e-6595-42f0-965f-282038d9247d","from":"sender@example.com","to":["recipient@example.com"],"cc":[],"bcc":[]}

FES can deal with the name and email address for all the from/to fields like Recipient Name <recipient@example.com>. Did you want to raise an issue with browser extension?

Originally posted by @Jerbell in https://github.com/FlowCrypt/flowcrypt-enterprise-on-prem/issues/2153#issuecomment-1018210504

related issues FlowCrypt/flowcrypt-android#1662 FlowCrypt/flowcrypt-ios#1337 #4268

[tomholub]

We should generally have names available in Contacts - let's format a mime recipient string for each recipient. The above is the json part of upload call when sending password protected message through FES.

[rrrooommmaaa]

So, regardless of the fact that the names (even if they are present in the contacts database) aren't displayed here

you still want to include them into the message?
Not very good, as the contact may be named in a way that the sender wouldn't want to show.
The sender should at least see what he's sending.

[tomholub]

If you think we should first make sure to display the names here, I'm open to doing that first. Could do what Google does - show only first name in collapsed view, and the whole thing in expanded view.