Update django-allauth to 0.35.0

[pyup-bot]

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

These links might come in handy: PyPI | Changelog | Repo

Changelog

0.35.0

---

Security notice

• As an extra security measure on top of what the standard Django password reset
  token generator is already facilitating, allauth now adds the user email
  address to the hash such that whenever the user's email address changes the
  token is invalidated.

Note worthy changes

• New provider: Azure, Microsoft Graph, Salesforce, Yahoo.

0.34.0

---

Security notice

• The "Set Password" view did not properly check whether or not the user already
  had a usable password set. This allowed an attacker to set the password
  without providing the current password, but only in case the attacker already
  gained control over the victim's session.

Note worthy changes

• New provider: Meetup.

0.33.0

---

Note worthy changes

• Security: password reset tokens are now prevented from being leaked through
  the password reset URL.

• New providers: Patreon, Authentiq, Dataporten.

• Dropbox has been upgraded to API V2.

• New translation: Norwegian.

Backwards incompatible changes

• Dropped support for Django 1.9.

0.32.0

---

Note worthy changes

• Improved AJAX support: the account management views (change/set password,
  manage e-mail addresses and social connections) now support AJAX GET requests.
  These views hand over all the required data for you to build your frontend
  application upon.

• New providers: Dwolla, Trello.

• Shopify: support for per-user access mode.

Backwards incompatible changes

• In previous versions, the views only responded with JSON responses when
  issuing AJAX requests of type POST. Now, the views also respond in JSON when
  making AJAX GET requests.

• The structure of the response for AJAX requests has changed. Previously, it
  contained a form_errors key containing all form validation errors, if any.
  Now, it contains a form key that describes the complete form, including
  the fields. Field specific errors are placed in
  form.fields['some_field'].errors, non-field errors in form.errors.

• The parameters passed to the Facebook JS SDK FB.init() method used to contain
  cookie, status, and xfbml, all set to true. These parameters
  are no longer explicitly passed. You can use the newly introduced INIT_PARAMS
  provider setting to provide your own values.

0.31.0

---

Note worthy changes

• Added a new user_logged_out signal.

• OpenId: Added support for requesting additional data.

• New providers: Auth0, Box, Line, Naver, Kakao, Daum, MailChimp, Eventbrite.

Backwards incompatible changes

• Django 1.7 / Python 3.2 compatibility has been dropped.

• Due to providers being registered in the same file as their definition
  it was impossible to subclass a provider without having the parent be
  registered. This has been addressed. If you have implemented a custom
  provider, you will need to change
  providers.registry.register(CustomProvider)
  into
  provider_classes = [CustomProvider].

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

Happy merging! 🤖