Allauth upgrade issue: MariaDB does not support unique constraints with conditions

[jmcarson]

When deploying the upgrade to allauth we saw the following warning:

WARNINGS:
account.EmailAddress: (models.W036) MariaDB does not support unique constraints with conditions.
HINT: A constraint won't be created. Silence this warning if you don't care about it.

Info in allauth ticket here: pennersr/django-allauth#3385 unfortunately just suggests upgrading to postgres

After reading through the various tickets I don't think that this would necessarily affect our sites in an adverse fashion, but there are a couple things we can do:

• Capture warnings that occur during migrate in our ci
• Handle this warning after further review of the issue and it's impact

[jmcarson]

It is difficult to capture the warnings as part of our current testing as they actually occur as part of the 'check' framework in django. You can recreate by running the following which happens prior to migrations when you run migrate:
manage.py check --database default

We can add this to our ci with the additional flag --fail-level WARNING

Then we could silence the warning by adding it to the SILENCED_SYSTEM_CHECKS list in the django config. Downsides are if this particular warning occurs due to some other change we will have silenced the warning already (as you cannot be more granular in what you silence).