Add email alerts on application server errors

[suecarmol]

Description

Added a setting in the production and staging environments that allow sending an email whenever there is an application error.

Rationale

This will help track any errors that may occur in the application.

Phabricator Ticket

T258144

How Has This Been Tested?

TBD

Screenshots of your changes (if appropriate):

N/A

Types of changes

What types of changes does your code introduce? Add an x in all the boxes that apply:

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

[jsnshrmn]

These images were already being published separately:
https://hub.docker.com/r/wikipedialibrary/externallinks/tags
https://hub.docker.com/r/wikipedialibrary/eventstream/tags

[jsnshrmn]

okay, I've reworked our docker-related variable names and verified that this is pushing the correct images to dockerhub when I overwrite staging with it.
I did

docker system prune --all --force 
docker pull wikipedialibrary/eventstream:branch_staging
docker pull wikipedialibrary/externallinks:branch_staging
docker-compose up

and was able to get a working deployment without building anything.

I did find that we currently can have problems if we have workflow overruns between commits. I spun my wheels for a while trying to get an environment variable injected into a gh artifact name. I don't have this solved, but basically, we should be able to add a commit sha or action run id into the artifact name. It just doesn't seem to be working as I'd expect based on the documentation.

https://github.com/actions/upload-artifact#environment-variables-and-tilde-expansion
https://docs.github.com/en/actions/reference/context-and-expression-syntax-for-github-actions#env-context

[suecarmol]

I think I managed to inject a run_id into the artifact names. Is this what you meant? Let me know if I need to make any additional changes.

[jsnshrmn]

Thanks! That's exactly what I was hoping to accomplish! Maybe the env context is only available to tasks running in a shell? This looks good from the github actions perspective!

[jsnshrmn]

Fat-fingered the close button!

[suecarmol]

Before merging this to master, I would like to test this out on the staging environment. Otherwise, I think this PR is ready to merge

[jsnshrmn]

Okay, I deployed a new staging environment with the current staging branch. I updated the project wiki notes as well.
https://github.com/WikipediaLibrary/externallinks/wiki/Debian-Server-Setup
Note that this will not currently pull new images automatically, as we talked about adding backups first.

[jsnshrmn]

Should use project and environment specific email addresses. See inline suggestions.

[jsnshrmn]

This is looking great! Thanks for your work!