Django-phonenumber-field

------------------
* Make ``formfields.PhoneNumberField`` honor ``PHONENUMBER_DEFAULT_REGION``
* Use ``PHONENUMBER_DEFAULT_REGION`` for example phone number in form field errors.
* Add support for Django 4.0
* Add Persian (farsi) translations.
* Update uk_AR translations

**Backwards incompatible changes**

* Drop support for Python 3.6

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

* Add support for Python 3.10
* Update Czech, Dutch and pt_BR translations

**Backwards incompatible changes**

* ``formfields.PhoneNumberField`` with a ``region`` now display national phone
numbers in the national format instead of ``PHONENUMBER_DEFAULT_FORMAT``.
International numbers are displayed in the ``PHONENUMBER_DEFAULT_FORMAT``.

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

* Lazy load ``formfields.PhoneNumberField`` translation for ``invalid`` data.
* Update Russian translations

**Backwards incompatible changes**

* Drop support for end-of-life Django 3.0

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

* Allow sorting ``PhoneNumber``\ s from Python
* Add support for Python 3.9 and Django 3.2
* Add Argentinian, Bulgarian, Indonesian, Ukrainian translations
* Update Esperanto and European Spanish translations

**Backwards incompatible changes**

* Drop support for Python 3.5

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

* Add support for Django 3.1.
* Fix rendering ``PhonePrefixSelect`` with ``initial`` passed to the
constructor.
* The Babel dependency is now optional.
* Switched to setuptools declarative configuration for packaging and
installation.
* Add Arabic and Russian translation.
* Correct License information in package metadata.

**Backwards incompatible changes**

* Drop support for end-of-life Django 1.11 and 2.1.
* As the Babel dependency is now optional, you must now install it to use
``PhoneNumberPrefixWidget``. If you do not install it, an
``ImproperlyConfigured`` exception will be raised when instantiated.

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

The big version bump is due to the change in how invalid phone numbers are handled.
Starting with ``2.4.0`` we added very aggressive validation, which raised ``ValueError``
for invalid numbers. This caused problems in unexpected places (like when filtering a
queryset). Starting with ``4.0.0`` we acknowledge that we can not completely prevent
invalid numbers from entering the system. Changes directly to the database, validation
changes in the upstream phonenumbers library, changes in the django settings may all
lead to invalid numbers in the database. Now it is possible to save an invalid number
to the database and ``__str__`` and ``__repr__`` clearly indicate invalid numbers.

* Don’t raise ``ValueError`` on invalid phone numbers - ``__str__`` and ``__repr__``
updated to report invalid phone numbers correctly if detected.
* Various translation updates