MailsControl: address some more problems

What does this MR do?

Addresses some causes for deprecation warnings. Also fixes the remaining body_html = null constraint issue. Finally, it now moves weird emails that cause parsing failures to a separate inbox instead of deleting them, so they can be analyzed.

How confident are you it won't break things if deployed?

Shouldn't break anything more than it already is broken :)

Links to related issues

#1532 (closed) (maybe closes, but should be determined manually through observation over the next few days :) )

How to test

Send some broken mails and check the cronjob's logs

Checklist

• added a test, or explain why one is not needed/possible...
• no unrelated changes
• asked someone for a code review
• set a "for:" label to indicate who will be affected by this change
• added to the next milestone (see https://gitlab.com/foodsharing-dev/foodsharing/-/milestones, unless it has a "for:Dev" label)
• added an entry to CHANGELOG.md
• added a short text that can be used in the release notes
• Once your MR has been merged, you are responsible to create a testing issue in the Beta Testing forum: https://foodsharing.de/?page=bezirk&bid=734&sub=forum. Please change the MRs label to "state:Beta testing".
  • Consider writing a detailed description in German.
  • Describe in a few sentences, what should be tested from a user perspective.
  • Also mention different settings (e.g. different browsers, roles, ...) how this change can be tested.
  • Be aware, that also non technical people should understand.

Release notes text in German

Eingehende Mails werden nun etwas zuverlässiger verarbeitet.