Email notifications stopped

[MarceloRobert]

The email notifications have stopped on March 03, this coincides with the interval where we were working with the deployment so that's a probable cause.

We should check it and restart sending emails as soon as possible.

[MarceloRobert]

Emails are back. There were a couple of problems that had to be solved:

1. The cronjobs did not log to the container, so we weren't able to see what was going on
2. Some cronjobs weren't able to access the SQLite file (which is used to check which notifications were already sent), and this happened because of a wrong default on environment variables
3. We changed the deployment structure from using separate env files to using a single .env. With that, some variables were not moved from the individual file to the combined one, leaving things like email variables not properly set.
4. The email credentials have changed for production, but the new ones required special character scaping which wasn't predicted
5. Finally, even with all the correct settings, there were some bugs in the kcidb pipeline which stopped data flow from the maestro origin, so there was no data to pull from for the emails of that specific origin.

We will be adding monitoring and automatic checks for these email notifications so that this doesn't happen again. And in the meantime, we will keep checking on them everyday so that we don't miss any problems.