Test mysql & sqlite

First off: This commit set changes the default development database backend to mysql. sqlite, however, is still completely supported with the caveat that a user must now modify config.dev to use the sqlite backend.

While looking into this, it was discovered that our SQLAlchemy backend for mysql (mysql-connector) completely broke model attributes when we switched to utf8mb4_bin (binary) -- it does not correct the correct conversion to and from binary utf8mb4.

The new, replacement dependency mysqlclient does. mysqlclient is also recommended in SQLAlchemy documentation as the "best" one available.

The mysqlclient backend uses a different exception flow then sqlite, and so models now raise IntegrityError when it finds problematic nulls (to centralize the exception logic).

In addition, now mysql and sqlite are both tested in CI. Docker hasn't been modified yet due to incoming changes to its config.

aurweb/models/accepted_term.py

+from sqlalchemy.exc import IntegrityError
 from sqlalchemy.orm import mapper
 
 from aurweb.db import make_relationship
@@ -11,7 +12,19 @@ class AcceptedTerm:
                  User: User = None, Term: Term = None,
                  Revision: int = None):
         self.User = User
+        if not self.User:
+            raise IntegrityError(
+                statement="Foreign key UserID cannot be null.",
+                orig="AcceptedTerms.UserID",
+                params=("NULL"))
+
         self.Term = Term
+        if not self.Term:
+            raise IntegrityError(
+                statement="Foreign key TermID cannot be null.",
+                orig="AcceptedTerms.TermID",
+                params=("NULL"))
+
         self.Revision = Revision