Bump django-taggit from 1.2.0 to 6.0.0

[dependabot]

Bumps django-taggit from 1.2.0 to 6.0.0.

Changelog

Sourced from django-taggit's changelog.

6.0.0 (2024-07-27)

* By default, order tag items on instances by the primary key. This generally means that they will be ordered by "creation date" for the tag item.
  The previous behavior for this was that by default tag items were not ordered. In practice tag items often end up ordered by creation date anyways, just due to how databases work, but this was not a guarantee.
  If you wish to have the old behavior, set ``ordering=[]`` to your ``TaggableManager`` instance.
  We believe that this should not cause a noticable performance change, and the number of queries involved should not change.
* Added the ability to merge tags via the admin
* Add Django 5.0 support (no code changes were needed, but now we test this release).
* Add Python 3.12 support
* Add support for dumpdata/loaddata using natural keys
5.0.1 (2023-10-26)

• Fix the package metadata to properly reflect the right Django and Python version requirements Release 5.0.0 improperly stated its Django bounds as >=3.2, so people installing without bounds will end up on a version that won't work.

5.0.0 (2023-10-24)

* **Backwards icompatible:** Rename the (``content_type``, ``object_id``) index on ``TaggedItem``.
  It is very unlikely for this to affect your code itself, and a migration will rename the index. This should not cause any downtime according to my research (Postgres does not lock the table for index renames, and Oracle holds a tiny lock to do it, and the change is only to the metadata, so is not dependent on table size).


Backwards incompatible: Remove the .index_together and .unique_together attributes on TaggedItem
We are instead using constraints and indexes to set up these properties.


Remove support for Django 3.2.


Remove usage of deprecated APIs for Django 4.2


Remove support for Python 3.7 (no code changes involved)


Fix tag_kwargs and TAGGIT_CASE_INSENSITIVE=True discrepency.


4.0.0 (2023-05-04)

• Remove Python 3.6 support (no code changes occurred, but we no longer test this release).
• Remove Django 4.0 support (no code changes occurred, but we no longer test this release).
• Add Django 4.2 support.

3.1.0 (2022-11-08)

* Add Python 3.11 support (no code changes were needed, but now we test this release).
* Add Django 4.1 support (no code changes were needed, but now we test this release).
* Fixed an issue where object caches would not be properly cleared after updating tags, leading
  to stale reads in cases where ``prefetch_related`` is used.
* Change ``TagListSerializerField`` to be a subclass of ``ListField``. This should improve support for API document generation. This change should not affect API behavior, but might affect metaprogramming code, so please procede carefully during this update.
3.0.0 (2022-05-02)

• Backwards incompatible: Tag slugification used to silently strip non-ASCII characters

... (truncated)

Commits

• ffa9d60 Merge pull request #910 from jazzband/prepare-release
• e764c3b Prepare version 6.0.0
• c02ffe5 Merge pull request #904 from jazzband/899-merge-tags
• ba48993 isort fix
• c6c7bb2 Fix issue when merging tags when the item has both the old and new tag
• b2906a9 Merge pull request #905 from Trafire/708-natural-keys-support
• 15ed6e5 Clean up documentation
• c2147e8 Add documentation details
• 5ead624 708 - natural_key return type changed to string instead of generator to allow...
• 4437d48 adding a small note under text field
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #1650.