Update django-allauth to 0.26.1

[pyup-bot]

There's a new version of django-allauth available.
You are currently using 0.25.2. I have updated it to 0.26.1

Changelog

0.26.1

---

Note worthy changes

• Locale files wrongly packaged, fixed.
• Fixed bug (KeyError) when ACCOUNT_SIGNUP_EMAIL_ENTER_TWICE was set to
  True.

0.26.0

---

Note worthy changes

• New providers: Weixin, Battle.net, Asana, Eve Online, 23andMe, Slack
• Django's password validation mechanism (see AUTH_PASSWORD_VALIDATORS) is now
  used to validate passwords.
• By default, email confirmations are no longer stored in the
  database. Instead, the email confirmation mail contains an HMAC
  based key identifying the email address to confirm. The verification
  lookup includes a fallback to the previous strategy so that there is
  no negative impact on pending verification emails.
• A new setting ACCOUNT_SIGNUP_EMAIL_ENTER_TWICE was added, requiring users to
  input their email address twice. The setting
  ACCOUNT_SIGNUP_PASSWORD_VERIFICATION has been renamed to
  ACCOUNT_SIGNUP_PASSWORD_ENTER_TWICE.
• New translations: Latvian, Kyrgyz.

Backwards incompatible changes

• Dropped support for Django 1.6
• In order to accomodate for Django's password validation, the
  clean_password method of the adapter now takes an (optional)
  user parameter as its second argument.
• The new HMAC based keys may contain colons. If you have forked
  account/urls.py, be sure to sync the account_confirm_email
  pattern.

Got merge conflicts? Close this PR and delete the branch. I'll create a new PR for you.

Happy merging! 🤖

[mention-bot]

@pyup-bot, thanks for your PR! By analyzing the annotation information on this pull request, we identified @requires and @ad-m to be potential reviewers