Django-queryable-properties

------------------

- Added the ``prefetch_queryable_properties`` utility function which allows to efficiently query property values for
model instances that were already loaded from the database beforehand
- Extended the ``LookupFilterMixin`` to allow to define a filter function/method that handles all lookups that don't
use an explicitly registered function/method
- Values for queryable properties with setters can now also be set using initializer keyword arguments of their
respective models

------------------

- Fixed the ``AnnotationGetterMixin`` and its subclasses to be able to work with nested properties correctly regardless
of whether or not the model's base manager uses the queryable properties extensions
- Fixed the admin filter that displays all possible options to be able to work with nested properties correctly
regardless of whether or not the model's default manager uses the queryable properties extensions

------------------

- Added support for Django 3.2
- Queryable properties can now define a verbose name that can be used in UI representations
- Added a Django admin integration that allows to reference queryable properties like regular model fields in various
admin options
- Fixed the construction of ``GROUP BY`` clauses when using annotations based on aggregate queryable properties in
Django 1.8

------------------

- Added an option to implement annotation-based properties that use their annotation to query their getter value from
the database
- Added a new ready-to-use queryable property implementation for properties that check whether or not certain related
objects exist (``RelatedExistenceCheckProperty``)
- Added a new ready-to-use queryable property implementation for properties that map field/attribute values to other
values (``MappingProperty``)

------------------

- String representations of queryable properties do now contain the full Python path instead of the Django model path
(also fixes an error that occurred when building the string representation for a property on an abstract model that
was defined outside of the installed apps)

------------------

- ``ValueCheckProperty`` and ``RangeCheckProperty`` objects can now take more complex attribute paths instead of simple
field/attribute names
- ``RangeCheckProperty`` objects now have an option that determines how to treat missing values to support ranges with
optional boundaries
- Added a new ready-to-use queryable property implementation for properties based on simple aggregates
(``AggregateProperty``)