Django-pgtrigger

Fixes

- Support proxy models with non-model or abstract inheritance by [g-nie](https://github.com/g-nie) and [SafaAlfulaij](https://github.com/SafaAlfulaij) in [#158](https://github.com/Opus10/django-pgtrigger/pull/158) and [#154](https://github.com/Opus10/django-pgtrigger/pull/154).
- Fix makemigrations issues with Django 5.1 by [pfouque](https://github.com/pfouque) in [#165](https://github.com/Opus10/django-pgtrigger/pull/156).

Changes

- Django 5.1 testing, dropped Django 3.2 / Postgres 12 support by [wesleykendall](https://github.com/wesleykendall) in [#157](https://github.com/Opus10/django-pgtrigger/pull/157).

Trivial

- Fix ReadTheDocs builds. [Wesley Kendall, 9c7f377]

Feature

- Django 5.0 compatibility [Wesley Kendall, 2e1366e]

Support and test against Django 5 with psycopg2 and psycopg3.

Trivial

- Change docs so that deferred (AFTER) triggers return NULL [Peter Thomassen, 59be2e9]
- Fix typo in cookbook (`exclude` instead of `filter`) [Peter Thomassen, 3714c08]
- Fix typo in docs model protection example [Peter Thomassen, 00b86af]
- Do additional error checking for arguments supplied to `FSM` trigger. [Wesley Kendall, e203834]

Bug

- Fix issues updating triggers in non-atomic migrations [Artem Streltsov, 888c4cf]

Fields of trigger conditions can now have their types updated in non-atomic migrations.

Feature

- Utilities to build trigger conditions based on field changes. [Wesley Kendall, 1471a35]

The following utility classes have been added to help trigger authors construct
trigger conditions based on changes to underlying fields:

- `pgtrigger.AnyChange`: If any supplied fields change, trigger the condition.
- `pgtrigger.AnyDontChange`: If any supplied fields don't change, trigger the condition.
- `pgtrigger.AllChange`: If all supplied fields change, trigger the condition.
- `pgtrigger.AllDontChange`: If all supplied fields don't change, trigger the condition.

A section in the docs was added for more examples on their use.