Email cleanup tracking

• Audit admin/accounts/build email addresses
• The ci email address goes solely to @joaocgreis. It would be good to find out what it's for, whether it gets any email, and who else might be added to it.
• Audit ci-alert email address
• The build-security address has @mmarchini and two other people who are (AFAIK) not active (@maclover7 and @gibfahn). It would be good to find out what it's for, whether it gets any email, and who else might be added to it.
• The security-ecosystem address goes to HackerOne. I don't believe it is taking any more reports. We should probably remove that email address? Or set up an auto-reply? Or maybe HackerOne sends a decent auto-reply?
• The user-feedback email address is likely unused?
• Are we still doing CrowdIn and the nodejs-crowdin email address? If so, are @zeke and @obensource still the right people for that email address? Are there others?
• Audit i18n similar to nodejs-crowdin .
• Audit github-bot. It's mostly inactive people. Is the email address used?
• The node-slack-bot address goes to one (inactive?) person (@gdams). Does it get any email? Would it make sense to add some other folks?
• The website-redesign email doesn't seem to have the current and active website-redesign people? Is that email even necessary? Seems like the GitHub team is sufficient.
• Audit zoom-nodejs. (Seems like a somewhat weird mix of people. Who is on there and why? What is the purpose of the email address?)

Originally posted by @Trott in https://github.com/nodejs/email/issues/181#issuecomment-1048829855

Start by reviewing the email configuration and the checklist entries for admin/accounts/build, ci, ci-alert, security-ecosystem, CrowdIn, i18n, github-bot, node-slack-bot, website-redesign, and zoom-nodejs. Audit each address's purpose, activity, and recipients; done means the open questions have decisions and the required cleanup or updates are recorded.