Django-field-audit

- Use batching by default for all bootstrap operations
- Add a `--batch-size` option to the bootstrap management command

- Add management command for bootstrapping
- Add new "top up" bootstrap action

- Fix migration constraint condition ordering which caused Django<4.0 to think
a new migration was needed.

- Add ability to bootstrap audit events for existing model records.

- Add Django compatibility tests.
- Add auditing support for "special" `QuerySet` write methods

- Remove `FieldChange` model in favor of storing the full delta on the
`AuditEvent` model.
- Add ability to define custom class paths for audited models.
- **IMPORTANT NOTE**: if you used version 0.2 to generate audit records, this
upgrade is destructive.

Version 0.2 was never used for production by the author, and migrating data
from that version to 1.0.0 is not implemented. If you wish to retain existing
(version 0.2) audit records, you will need to preserve those records and
migrate them yourself.

Upgrade from 0.2 (destroying existing data)

Steps to upgrade if you do _not_ wish to retain any existing data are as
follows:

shell
python manage.py migrate field_audit zero
pip install -U django-field-audit
python manage.py migrate field_audit


Upgrade from 0.2 (retaining existing data)

Steps to upgrade while retaining your existing data are as follows:

1. Run the following commands against your database to preserve the existing
`field_audit_auditevent` table:

sql
ALTER TABLE field_audit_auditevent RENAME TO field_audit_v02_auditevent;
ALTER SEQUENCE field_audit_auditevent_id_seq RENAME TO field_audit_v02_auditevent_id_seq;
ALTER INDEX field_audit_auditevent_pkey RENAME TO field_audit_v02_auditevent_pkey;
ALTER INDEX field_audit_auditevent_event_date_129a0da2 RENAME TO field_audit_v02_auditevent_event_date_129a0da2;
ALTER INDEX field_audit_auditevent_object_class_path_034c1566 RENAME TO field_audit_v02_auditevent_object_class_path_034c1566;
ALTER INDEX field_audit_auditevent_object_class_path_034c1566_like RENAME TO field_audit_v02_auditevent_object_class_path_034c1566_like;


2. Fake the zero migration for the `field_audit` app:

shell
python manage.py migrate field_audit zero --fake


3. Upgrade and run migrations:

shell
pip install -U django-field-audit
python manage.py migrate field_audit


4. Migrate your data from the old tables (`field_audit_v02_auditevent` and
`field_audit_fieldchange`) into the new `field_audit.models.AuditEvent`
model.