feat: Django 4.0, 4.1 / Python 3.10/3.11, mysql support, running tests on sqlite, postgres and mysql

[fsbraun]

Description

This PR extends the test suite considerably by introducing tests for Postgres and MySQL. It is a fix for #286 where a migration that fails to run on MySQL.

It turns out that some unit tests did neither run on Postgres nor MySQL, since they compared pk of Version objects with pk of the corresponding Content object which only accidentally worked on sqlite.

Features of the PR

• Extended tests running on sqlite, Postgres, MySQL
• Added tests for Django 4.0, 4.1, Python 3.10, 3.11
• Fix for Migration 009 fails on mysql #286

Checklist

• I have opened this pull request against master
• I have added or modified the tests when changing logic
• I have followed the conventional commits guidelines to add meaningful information into the changelog
• I have read the contribution guidelines and I have joined #workgroup-pr-review on
  Slack to find a “pr review buddy” who is going to review my pull request.

[codecov]

Codecov Report

Merging #287 (f82d312) into master (31f14df) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #287   +/-   ##
=======================================
  Coverage   86.60%   86.60%           
=======================================
  Files          23       23           
  Lines         799      799           
  Branches      105      117   +12     
=======================================
  Hits          692      692           
  Misses         81       81           
  Partials       26       26           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[Aiky30]

@fsbraun Can you add more details to the error / issue such as MySQL version and the database backend in use, for postgres this tends to be: django.db.backends.postgresql, although this is up to the project author: https://docs.djangoproject.com/en/4.1/ref/databases/#postgresql-connection-settings

I ask because this chnage doesn't single out MySQL and affects all DB's. Ideally we would try and avoid that.

[fsbraun]

I've added test for the mysql backend: django.db.backends.mysql and django.db.backends.postgresql. The fix now only affects the mysql backend. The tests run the migrations (that's why I added migrations for the test apps, too).

At this point it turned out that some tests were confusing Version object pk with Content object pk. I've fixed that.

[Aiky30]

Looks OK to me. Nothing blocking.

Some comments below.

The python version list maybe a little extreme. this is very wasteful on resources (not environmentally friendly). As this is Django 4.1 I guess we need to support what django do, so we could remove 3.7 at least. https://docs.djangoproject.com/en/4.1/releases/4.1/#python-compatibility

[Aiky30]

It's fine to change these, they were in the previous format because the Divio Cloud didn't like Pip urls, it's was more convenient to use the same urls across the projects i..e in and out of the Divio Cloud.

[fsbraun]

Was not aware of this. Will revert.

[Aiky30]

I don't think that the migrations are actually required for test packages, maybe this is a side affect of the testing issue not using postgres. Doesn't really matter to be fair.