Set app's default_auto_field to match current migrations

[blueyed]

Without this it would use DEFAULT_AUTO_FIELD from the project's
settings, where the default changed to BigAutoField.

docs: https://docs.djangoproject.com/en/3.2/ref/settings/#default-auto-field
ref: https://stackoverflow.com/a/67007098/15690

[codecov]

Codecov Report

Merging #138 (fb0e017) into master (2da6e3c) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #138   +/-   ##
=======================================
  Coverage   95.05%   95.06%           
=======================================
  Files          25       25           
  Lines         506      507    +1     
=======================================
+ Hits          481      482    +1     
  Misses         25       25           

Impacted Files	Coverage Δ
django_fsm_log/apps.py	100.00% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2da6e3c...fb0e017. Read the comment docs.

[MRigal]

@blueyed please see history of a previous PR at #132

[blueyed]

Ok, closing then.

FWIW: I'm using a customized app for this now:

from django_fsm_log.apps import DjangoFSMLogAppConfig


class ModifiedDjangoFSMLogAppConfig(DjangoFSMLogAppConfig):
    # Do not trigger a migration in 3rd party app.
    # (https://github.com/jazzband/django-fsm-log/pull/1328)
    default_auto_field = "django.db.models.AutoField"

Another solution might be to also adjust your project settings to keep using the previous default (AutoField).