Django-ordered-model

----------
- Fix `post_delete` signal triggered upshuffles to do a potentially expensive full reordering of the owrt group (307)
- Support passing custom `--batch_size` to `reorder_model` management command (303)
- Add tox builder for python 3.11, Django 4.1 and above
- Add `ordered_model.fields.OrderedManyToManyField` which respects `Meta.ordering` when following ManyToMany related fields. (277)
- Relax check that `order_with_respect_to` entries final element must be a `ForeignKey` - it can be any `Field` instance (298)

----------
- Relax Check for `OrderedModelManager` to a `Warning`, if the manager returns the correct queryset (290)

----------
- Restrict signal handler 'senders' to subclasses of `OrderedModelBase` to avoid query count regression due to `Collector.can_fast_delete` logic in `models/deletion.py` (288)
- Fix `reorder_model` management command re-ordering with multiple `order_with_respect_to` values

----------
- Fix a performance regression (unnecessary queries) in the WRT change detection (286)
- Add a Check that `order_with_respect_to` specifies only ForeignKey fields
- Add a Check that our subclasses of ModelManager and QuerySet are used (286)

----------

- Fix for `model.save()` falsely detecting WRT change from admin create since 3.7
- Cascaded deletes of `OrderedModel` instances now handled using signals (182)

----------

- Use bulk update method in `reorder_model` management command for performance (273)
- Add tox builder for python 3.10, use upstream DRF with upstream django
- Emit a system Check failure if a subclass of `OrderedModelBase` fails to specify `Meta.ordering`
- Updating the value of fields within `order_with_respect_to` now adjusts ordering accordingly (198)