feat: support Microsoft Graph API for emails

[sbliven]

Motivation

This adds support for Microsoft Graph API for sending emails. This is an alternative to SMTP for MS365 accounts that would otherwise require interactive OAuth logins, making it useful for automated emails.

Description

To use this you (or your azure admin) will need to generate a tenantId, clientId, and clientSecret with permissions to send email. The process is described here.

Email configuration is done with the following variables:

General settings:

EMAIL_TYPE: [string] Optional The type of your email provider. Values "smtp" or "ms365". Defaults to "smtp".

EMAIL_FROM [string] Optional Email address that emails should be sent from.

For SMTP emails:

SMTP_HOST [string] Optional Host of SMTP server.

SMTP_PORT [number] Optional Port of SMTP server. Defaults to 587.

SMTP_SECURE [boolean] Optional Use encrypted SMTPS. Defaults to "no".

The SMTP_MESSAGE_FROM field is still available as an alias for EMAIL_FROM for backwards compatibility.

For Microsoft 365 emails using the Graph API:

MS365_TENANT_ID` [string] Optional Tenant ID for sending emails over Microsoft Graph API.

MS365_CLIENT_ID` [string] Optional Client ID for sending emails over Microsoft Graph API.

MS365_CLIENT_SECRET` [string] Optional Client Secret for sending emails over Microsoft Graph API.

Note that the default is to use SMTP, so this is fully backwards compatible with existing configuration files.

Fixes

• Part of Implement PSI job actions #1124

Changes:

• Support emails via Microsoft Graph API.

Tests included

Emails are difficult to test without using an actual email address. I have tested this manually using my own address, but I haven't included any unit tests.

• Included for each change/fix?
• Passing?

Documentation

• swagger documentation updated (required for API changes)
• official documentation updated

official documentation info

• Document MS365 email settings documentation#62