Django-salesforce

------------------
* Add: Support for Django 5.1
* Change: The cursor rollback() method log messages are silenced by default
because they are mostly anoying in tests. They can be enabled again if
``settings.DATABASES['salesforce']['OPTIONS']['WARNING_ON_ROLLBACK'] == True``
* Changes where users will not know a difference:

* Refactored the backend.query to use consistent data types internally.
* Checked a development version of Django is really used by "tox -e djdev"
* Fix introspection for Salesforce API 62.0 Winter '25 (skip introspection of ...Event object that is not a table)

------------------
The main new features are in the improved query compiler

* Remove: the old Python 3.7
* Remove: the code for Django 2.0
* Fix: many issues in the query compiler in edge cases:

- fix a query with offset, but without a limit (NotImplementedError)
- fix a '__range' lookup on a field of custom foreign key object (SalesforceError)
- fix a '=null' lookup. It worked probably always correctly, but the old implementation was different from standard lookups. It made it impossible to distinguish it from unsupported queries
* Add: The query compiler is now much more precise. Most of unsupported queries will
write a warning before they are tried compiled. This is how users have
discovered some functional queries in the past.
No regression is known that a previously correct query would write a warning.
* Add: Support for date and datetime lookup by year, quarter, month, day, week_day, hour
e.g. group this year by month:
.filter(date__year=2024).value('date__month').annotate(total=Sum('amount'))
* Add: The method .sf(minimal_aliases=True) is not necessary
for ContentDocumentLink .filter(...); 259
* Fix: Compile correctly: .filter(related_model__field__in=...) Fix 302
* Fix: Prepare tests for Salesforce API 61.0 Summer '24
* Add: Introspect Salesforce fields of type Formula to sf_formula="..." parameter

------------------
* Add: Support for ``db_default`` field option in Django 5.0. It allows a seamless
support of the ``defaultedOnCreate`` counterpart in Salesforce.
* Add: Support for Salesforce API 60.0 Spring '24.
* Change: Values of ``FloatField`` are now really float, not Decimal as previously.
* Fix: Compatibility with the current django-debug-toolbar 322
* Fix: Introspection ``inspectdb`` of custom editable name fields 308
* Add: FloatField is used by ``inspectdb`` for some metadata with negative decimal places
that are new in API 60.0.
* Change: A license code is required also in the first half of lifetime of a LTS version
unless the AGPL licence is accepted.
Django 4.2 LTS will be unlocked together with unlocking 5.0 in August 2024
in Django-salesforce 5.1 release.
* Change: License code validity may not transfer to the next django-salesforce version
if sponsorship ended.

----------------
* Add: Support for Django 5.0
* Add: Monitoring 'api_usage' from 'Sforce-Limit-Info' API response header 317

----------------
* Add: Basic diagnostics after installation can be done by command
``python manage.py check --database=salesforce``
* Change: Use with Django 4.2 requires an enterprise license key.
* Add: Support for Django 4.2
* Use API 58.0 Summer '23
* Add: Support for Django Database caching 315
* Fix: Configurable max introspected pick-list size
SF_MAX_INSPECTDB_PICKLIST_LENGTH 312
Some people need to introspect huge picklists, some don't want.

----------------
* Add: Support for Django 4.1
* Add: Command ``inspectdb`` can introspect actual default values
of fields from a ``defaultValueFormula`` if it is a simple constant
like a number or a string.
* Fix: A default value ``DefaultedOnCreate(value)`` is no longer created
by ``inspectdb`` in favour of a simple ``value``. If a simple default value
can not be known then a generic ``DEFAULTED_ON_CREATE`` is still used rarely
for default values created by a complicated or unknown function only
on Salesforce side. 280
* Fix: Optionally don't use redundant table names before field names
if queried with ``.sf(minimal_aliases=True)``; important for some
special system objects 302
* Fix: Tests with the newest Django, Salesforce, Python; including Python 3.11(beta)
* Fix: Extended SalesforceModel with PostgreSQL backend and Django >= 3.0 299