Bumps [django-constance[database]](https://github.com/jazzband/django-constance) from 2.9.1 to 3.1.0.
- [Release notes](https://github.com/jazzband/django-constance/releases)
- [Changelog](https://github.com/jazzband/django-constance/blob/master/docs/changes.rst)
- [Commits](jazzband/django-constance@2.9.1...3.1.0)

---
updated-dependencies:
- dependency-name: django-constance[database]
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>

...as mentioned in `django-constance`'s changelog for v3.0.0:
https://django-constance.readthedocs.io/en/latest/changes.html#v3-0-0-2023-07-27.

As a side note, I found it weird that the tests passed, even though this
non-existent app was enabled in the settings. However, through a little
bit of experimentation, I found out that it seems like Django doesn't
care whether the modules listed in `INSTALLED_APPS` are actually apps
- i.e. that they contain a file (named `apps.py` by default) containing
a subclass of `AppConfig`.

The `[database]` extra was removed in `django-constance` v3.0.0, in this
commit:
jazzband/django-constance@2cb2ccd#diff-60f61ab7a8d1910d86d9fda2261620314edcae5894d5aaa236b821c7256badd7.