ESM: Viewing and sending emails from the new beta UI datacard view

User story:

As a user of Efecte's Service Management Tool (ESM) I want to enjoy a modern user interface for reading and creating emails in order to work not only effectively but also with delight.

AC's:

1. Visual presentation of the email previews in the datacard view

   1. If there is at least an attribute with EntityStateMail handler and an attribute with Worklog handler in the same class, the EntityStateMail handler should be presented as a tab. Worklog handlers should be also presented on tabs. 

      1. The tab label should be equal to the attribute name. The name should be translatable.  

      2. If the class has more than one attribute with entityStateMail, they should be shown as tabs

         1. In case the class has just one entityStateMail handler and no worklog handlers, then the entityStateMail should be shown without the tabs (without the bar with the tabs)

      3. The order of the tabs should be defined by the order of the attributes inside of the class

   2. Users should be able to view emails in chronological order in the detail view

      1. The most recent email is shown first on the list

      2. Emails should be grouped by "Today", "This week", "Older" :question_mark: 

         1. These headers should be shown even though there would be no emails. There should be a placeholder showing that there are no emails under the heading. 

   3. The user should be able to see the "from" information of each email. 

      1. If no person is found, the senders name and emails address should be shown without a link

      2. In case there is a person card for the sender, it should be shown as a reference (link). 

         1. The mail.addressbook.codes setting should be used for determining the template and attribute to be used for creating the link to the person

   4. The user should be able to see the timestamp (send/receive time) of the email 

   5. The user should be able to see a preview (one row, with line breaks removed) of each email 

   6. Users should be able to scroll the emails within the email box both with mobile devices and desktop

      1. Scroll bar should be visible and usable

   7. Users should be able to see a preview in a tooltip when hovering on the emails. The tooltip should contain the following information:

      1. Timestamp (Send/receive date and time) in the local, user-based timezone, format based on datetime.output.pattern

      2. FROM information (name + address) 

      3. TO information (name + address) 

      4. Subject

      5. Body including visual formatting and inline images

      6. List of attachments

2. Visual presentation of the detailed email view (floating window), reading emails and sending emails

   1. Users should be able to see all emails in a dedicated overlay by clicking on one of the emails or by selecting "New email" 

      1. The UI text for the "New email" button should be translatable as currently (presentation text)

      2. The user should be able to move around the overlay

   2. There should be an option to open the overlay in a separate browser window

      1. When opening the email overlay in a separate browser window, the overlay should not anymore be shown

   3. The visual presentation of the email previews should be similar in all cases (datacard view, overlay, separate browser window)

   4. There should be an option to download the .msg file

   5. The user should be able to remove emails

   6. The user should be able to see the TO, CC, BCC and from information in the email preview section

3. Creating and sending emails

   1. The user should be able to create a new email based on the EntityStateMail defaultConfiguration by selecting clicking "New email" or by selecting an email template, in case they have update or create permissions for the email attribute

      1. If several email templates have been defined then the user can select the email template

      2. The default email template should be applied to the case when the user does create a new emails, forward an email or reply/reply all to an email. 

         1. The user should have a possibility to select the email template when replying to an email

      3. The email template should be selectable also from an attribute, if the Mail templates attribute has been configured

      4. The attachments should be uploaded to the attribute defined in Uploaded attachments attribute setting

   2. The email body should be written by using a rich text editor

   3. Users should be able to edit the TO & CC & BCC email address when replying to an email, for example, double-clicking the already given address object 

      1. The user should be able to select the recipient from the addressbook. The mail.addressbook.codes setting should be applied.  

   4. The user should be able to edit the from field in case the From field editable setting is enabled

   5. Users should be able to reply, reply all, and forward the email by the click of a button

   6. Users should be able to mark an email as read or unread by clicking a button. The read/unread parameter is global as currently.

   7. The number of unread emails should be shown as a label

   8. Only rich text (html) format should be supported - no plain text emails should be supported

   9. Attachments are shown with their file name as links