Change Python 3.10 in Github action test ci matrix.

Remove unused code for Django < 2.0

* add django 4.0 to tox envs

* make `get_extra_restriction` work across django versions

 - add a shim around `get_extra_restriction` so that it works in
   versions of Django >=4 and <4
 - fixes #776

* update changelog & pypi classifiers

* fix typo in version check

updates:
- [github.com/pre-commit/pre-commit-hooks: v4.0.1 → v4.1.0](pre-commit/pre-commit-hooks@v4.0.1...v4.1.0)

* Fixed #784 -- Added migrations autodetected by Django 4.0

* [pre-commit.ci] auto fixes from pre-commit.com hooks

for more information, see https://pre-commit.ci

* Fixed import sorting

Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>

Prepare Django Taggit 2.1.0 Release

The old behaviour of assertQuerysetEqual automatically calling repr is deprecated in Django 3.2 https://docs.djangoproject.com/en/4.0/releases/3.2/#id3 and dropped in Django 4.1.

As of django/django@a697424 there are two new cached properties path_infos and reverse_path_infos which Django will use in preference to the get_path_info() and get_reverse_path_info() methods when not passing a filtered_relation argument. TaggableManager is patching these methods, and therefore it now needs to provide these cached properties to match Django's expectations.

These are introduced in django/django@a697424 to be used in preference to get_path_info / reverse_path_info when not passing filtered_relation.

Set transform=repr on assertQuerysetEqual (Dj4.1 compatibility)

Handle path_infos / reverse_path_infos cached properties (Dj4.1 compatibility)

updates:
- [github.com/psf/black: 21.12b0 → 22.3.0](psf/black@21.12b0...22.3.0)

…azy`

`django.utils.translation.ugettext_lazy` was deprecated in Django 3.0 and removed in Django 4.0 in favor of `django.utils.translation.gettext_lazy`.

updates:
- [github.com/pre-commit/pre-commit-hooks: v4.1.0 → v4.2.0](pre-commit/pre-commit-hooks@v4.1.0...v4.2.0)

Drop Django 2.2 support.

[pre-commit.ci] pre-commit autoupdate

 This change is motivated by the many many people using non-latin
languages who experience the (rather baffling) behavior of outright
stripping characters when generating slugs from stuff that doesn't
fit into ASCII.

 We went through loads of pain as a programming community to get to
nicely supporting unicode everywhere, it's time to take advantage of
that fact and just let people have stuff appear in their native
language as much as possible.

Preserve unicode when slugifying by default

Prepare the release of Version 3.0.0

Clear prefetch cache on tag updates

updates:
- [github.com/pre-commit/pre-commit-hooks: v4.2.0 → v4.3.0](pre-commit/pre-commit-hooks@v4.2.0...v4.3.0)
- [github.com/psf/black: 22.3.0 → 22.6.0](psf/black@22.3.0...22.6.0)

[pre-commit.ci] pre-commit autoupdate

There are small typos in:
- docs/faq.rst
- taggit/managers.py
- tests/tests.py

Fixes:
- Should read `stored` rather than `storred`.
- Should read `intermediary` rather than `intermeidary`.
- Should read `function` rather than `funtion`.

Signed-off-by: Tim Gates <[email protected]>

docs: Fix a few typos

updates:
- [github.com/PyCQA/flake8: 4.0.1 → 5.0.4](PyCQA/flake8@4.0.1...5.0.4)

[pre-commit.ci] pre-commit autoupdate

Do not display outdated unicode strings in the documentation.

updates:
- [github.com/psf/black: 22.6.0 → 22.8.0](psf/black@22.6.0...22.8.0)

updates:
- [github.com/psf/black: 22.8.0 → 22.10.0](psf/black@22.8.0...22.10.0)

Fix typo

[pre-commit.ci] pre-commit autoupdate

Add Python 3.11 to CI, tox, and trove classifiers

 This is a tricky change, I tried to confirm that behavior changes
 aren't occuring with this, but really we might end up finding issues
 when the rubber hits the road.

 This should make it clearer if an upgrade is needed or not.

Make TagListSerializerField subclass ListField

 This also updates some of the contributing docs

Prepare 3.1.0 release

Add pyupgrade and django-upgrade pre-commmit hook

updates:
- [github.com/asottile/pyupgrade: v2.37.3 → v3.2.2](asottile/pyupgrade@v2.37.3...v3.2.2)
- [github.com/adamchainz/django-upgrade: 1.7.0 → 1.12.0](adamchainz/django-upgrade@1.7.0...1.12.0)

for more information, see https://pre-commit.ci

[pre-commit.ci] pre-commit autoupdate

to support Django 5.0 (unreleased).

The _columns() versions are still retained for compatibility across Django
versions.

Ref: django/django@8b1ff0d

Update Django Support

Fix faq.rst indentation

Prepare Release 4.0.0

updates:
- [github.com/pre-commit/pre-commit-hooks: v4.3.0 → v4.4.0](pre-commit/pre-commit-hooks@v4.3.0...v4.4.0)
- [github.com/psf/black: 22.10.0 → 23.7.0](psf/black@22.10.0...23.7.0)
- [github.com/PyCQA/flake8: 5.0.4 → 6.0.0](PyCQA/flake8@5.0.4...6.0.0)
- [github.com/asottile/pyupgrade: v3.2.2 → v3.9.0](asottile/pyupgrade@v3.2.2...v3.9.0)
- [github.com/adamchainz/django-upgrade: 1.12.0 → 1.14.0](adamchainz/django-upgrade@1.12.0...1.14.0)

Fix `tag_kwargs` and case insensitive discrepancy

[pre-commit.ci] pre-commit autoupdate

Add migration files for tests

 This is a database no-op

 This shouldn't affect anything outside of tests

This reverts commit 7ff7c86.