feat: Naive attempt to add SES role based auth for emails, instead of SMTP.

[cafuego]

Perhaps this should be in config, and pass a single mail transport back to the module.

Refs: OPS-10025

[rupl]

I'd tend to agree it should be in config, but I also don't have so strong of an opinion. I added the deps and linted for you. Should we deploy an image of this to dev and see if it works? Is it even possible to test when mailhog is scooping up emails?

[cafuego]

Sadly, no. There is no way to test this change with mailhog. When mail is handled via SES api calls, the data is handed off to an AWS service endpoint and the only thing we know is the API response code and the (eventual) log in ELK. There is no way to intercept that.

To make things worse, the there is no test endpoint to do a dry run with; to check whether or no the API calls work or fail there are magic destination email address that will trigger a success or fail. Any other email addresses will cause an actual email to be delivered.

That means we cannot test this with an actual HID database; at best we can spin up an env with only our own accounts in it and make it send mail.