Update django-model-utils to 4.5.1

[pyup-bot]

This PR updates django-model-utils from 4.0.0 to 4.5.1.

Changelog

4.4.0

------------------

- Add support for `Python 3.11` (GH-545)
- Add support for `Python 3.12` (GH-545)
- Drop support for `Python 3.7` (GH-545)
- Add support for `Django 4.2`
- Add support for `Django 5.0`
- Remove ``SaveSignalHandlingModel``. This model used a modified copy of the internal Django method `Model.save_base()`
and had not been updated for upstream bug fixes changes since its addition.
- Add Swedish translation
- Use proper column name instead of attname (GH-573)
- Fix ValueError when calling prefetch_related for tracked ForeignKey fields

4.3.1

------------------

- Confirm support for `Django 4.0`
- Add Spanish translation
- Add French translation
- Drop Django 1.7 workaround from `select_subclasses()`
- Drop support for `Django < 3.2`
- Drop support for `Python 3.6`
- Confirm support for `Django 4.1`

4.3.0

-----

- Never released due to packaging issues.

4.2.0

------------------

- Add support for `Django 3.2`
- Drop support for `Django 3.0`
- Add support for `Python 3.10`
- Added urlsafe token field.
- Introduce context manager for FieldTracker state reset (GH-491)
- Fix performance regression of FieldTracker on FileField subclasses on Django 3.1+
(GH-498)

4.1.1

------------------

- Applied `isort` to codebase (Refs GH-402)
- Fix `TypeError` in save when model inherits from both TimeStampModel
and StatusModel. (Fixes GH-465)

4.1.0

------------------

**Breaking changes:**

- `FieldTracker` now marks fields as not changed after `refresh_from_db`
respecting `fields` argument (GH-404)
- `FieldTracker` now respects `update_fields` changed in overridden `save()`
method (GH-404)
- `FieldTracker` now resets states after `pre_save()` and not anymore `save()`
signals, possibly altering the behaviour of overridden `save()`
methods (GH-404)

**Other changes:**

- Update InheritanceQuerySetMixin to avoid querying too much tables
- TimeStampedModel now automatically adds 'modified' field as an update_fields
parameter even if it is forgotten while using save()
- Replace ugettext_lazy with gettext_lazy to satisfy Django deprecation warning
- Add available_objects manager to SoftDeletableModel and add deprecation
warning to objects manager.
- StatusModel now automatically adds 'status_changed' field during save as an
update_fieldsparameter when 'status' is present in it to make sure it is not
forgotten.
- Update test requirements
- Move tests to GitHub Actions: https://github.com/jazzband/django-model-utils/actions
- Drop support for `Django 2.1`
- Add support for `Python 3.9`
- Add support for `Django 3.1`

Links

• PyPI: https://pypi.org/project/django-model-utils
• Changelog: https://data.safetycli.com/changelogs/django-model-utils/
• Repo: https://github.com/jazzband/django-model-utils

[pyup-bot]

Closing this in favor of #238