Add an `alternate_emails` array to the Member object in `members.json`

Summary

By adding an alternate_emails key, we can make it so that we can use emails that are not considered from an approved domain.

Reasoning

Sometimes people can't access Google Workspace using their approved domain email, or they prefer to use a different email entirely. We would not promote alternative emails to the public; however, alternative emails would still be available on GitHub or on our website's members.json file.

This would also help admin with ensuring we use the proper emails for proper things. (i.e.: alternate email for requested reason, approved domain email for everything else)

All information about Ojos Project-related stuff should be found in the members.json file, so this would continue that precedent.

Concept images and/or code

Members should provide EXPLICIT permission and understand that although we wouldn't promote their alternate email address, it would still be made public.

Concept code to be added to a Member object:

{
    "alternate_emails": [{"email": "some@gmail.com", "reason": "Google Calendar invites"}]
}

ojosproject / website