Django-heroku-connect

What's Changed
* Update Actions to resolve warnings by pcrock-thmdo in https://github.com/thermondo/django-heroku-connect/pull/115
* **BREAKING:** add support for Django 4.x & python 3.11, drop unsupported django versions by syphar in https://github.com/thermondo/django-heroku-connect/pull/114


**Full Changelog**: https://github.com/thermondo/django-heroku-connect/compare/0.26.0...1.0.0

What's Changed
* add python 3.10 to the test matrix, replace tox with plain GH actions by syphar in https://github.com/thermondo/django-heroku-connect/pull/110
* Make DB port configurable, specify upper bound for Django version by pcrock-thmdo in https://github.com/thermondo/django-heroku-connect/pull/113
* Convert Composed query to str before running raw query by pcrock-thmdo in https://github.com/thermondo/django-heroku-connect/pull/112

New Contributors
* pcrock-thmdo made their first contribution in https://github.com/thermondo/django-heroku-connect/pull/113

**Full Changelog**: https://github.com/thermondo/django-heroku-connect/compare/0.25.0...0.26.0

- Update CI test matrix: Add Django 3.2, drop Python 3.6, Django 3.0 107
- move linting to pre-commit, add black and run it 109

- migrate to GitHub actions, add python 3.9 and Django 3.1 (104)
- [doc] Add a note on Django signals (105)
- Replace deprecated Django `ugettext_lazy` (106)

- change field-type for values on trigger-log tables ( 103 ) **backwards incompatible change!**
- new triggerlog `.redo` functionality broke when retrying on objects with read-only fields ( 102 )

Replace `models.NullBooleanField` usage in favor of `models.BooleanField(null=True)` (Django 4.0 deprecation warning)