Invalid emails updating: Nova and APP

Example: https://completetuition.slack.com/archives/C02M389PNN9/p1773400351031579

Outline of issue:

Email for a user cannot be updated, Nova error message: 'Email is invalid'

Steps to address:

1. Check with user that the email is definitely the one they intend to use
2. Check whether email is valid/invalid using a website such as https://mxtoolbox.com/
   1. This website checks the validity of the domain name (i.e the section of an email after the '@'. E.g gmail.com)
3. If 2 returns the domain as valid, check that the characters in the email prefix (before the '@') are valid
   1. see allowed characters here: https://en.wikipedia.org/wiki/Email_address#:~:text=Force%20(IETF).-,Local%2Dpart,-%5Bedit%5D

   2. The local-part of the email address may be unquoted or may be enclosed in quotation marks.

      If unquoted, it may use any of these ASCII characters:

      • uppercase and lowercase Latin letters A  to Z  and a  to z
      • digits 0  to 9
      • printable characters !#$%&'*+-/=?^_`{|}~

      • dot . , provided that it is not the first or last character and provided also that it does not appear consecutively (e.g., John..Doe@example.com  is not allowed).

        If quoted, it may contain Space, Horizontal Tab (HT), any ASCII graphic except Backslash and Quote and a quoted-pair consisting of a Backslash followed by HT, Space or any ASCII graphic; it may also be split between lines anywhere that HT or Space appears. In contrast to unquoted local-parts, the addresses ".John.Doe"@example.com , "John.Doe."@example.com  and "John..Doe"@example.com  are allowed.

      • The maximum total length of the local-part of an email address is 64 octets.
        • Space and special characters "(),:;<>@[\]  are allowed with restrictions (they are only allowed inside a quoted string, as described in the paragraph below, and in that quoted string, any backslash or double-quote must be preceded once by a backslash);
        • Comments are allowed with parentheses, either at the start or end of the local-part; e.g., john.smith(comment)@example.com  and (comment)john.smith@example.com  are both equivalent to john.smith@example.com .
4. If either of step 2 or 3 return that the email is invalid - go back to the user with this information.
   1. It is part of our process that invalid emails should not be accepted by the platform.

5. If both the prefix and domain are valid:

   Forward the issue on to the development team and confirm these above checks have been made