Maintenance: security updates across the stack, three PayGlue-OS releases

We went through every library PayGlue is built on and brought it up to date, in the hosted product first and then in the open source edition. That closed all open security advisories in both repositories. Most of them concerned code paths PayGlue does not use, or tools that only run in our test suite. The hosted product now runs on Django 6.1.1 and gunicorn 26, and the open source edition runs the same versions, so there is one stack to test instead of two. Nothing changes for you and there is nothing you need to do.

• All open security advisories closed, in the hosted product and in PayGlue-OS
• Django 6.1.1, gunicorn 26.2 and current versions of the other libraries
• The open source edition runs the same versions as the hosted product
• PayGlue-OS v0.7.1: security and patch updates
• PayGlue-OS v0.8.0: Django 6.1, gunicorn 26, django-tenants removed
• PayGlue-OS v0.9.0: test purchases are labelled, delivery alerts are retried