www/py-django32: Switch consumers over to Django 3.2

[kai]

Summary

Django 2.2 will become End-of-Life during April 2022 and Django 3.2
is the new LTS (= Long Term Support) release which will be supported
until April 2024.

* Switch the most ports that use www/py-django22 to www/py-django32
* Switch www/seahub over to www/py-djangorestframework
* Fix pkg-plist issues with deskutils/py-paperless
* Ports that aren't yet ready for Django 3.2 and deprecated ports were
  excluded.

PR: 261313

Test Plan

• Most ports were updated/checked for Django 3.2 compatibility during 2022Q1, see also https://wiki.freebsd.org/Ports/Django/Django32Migration
• Bulk run against all consumers and reverse dependencies -> OK

Notes:

Excluded ports because they aren't compatible with Django 3.2, yet:

• www/py-django-ldapdb
• www/py-django-modern-rpc
• www/py-django-tagging
• www/py-graphite-web

Excluded ports because they're deprecated with an expiration date:

• www/py-django
• www/py-django-babel
• www/py-django-bootstrap-form
• www/py-django-bulk-update
• www/py-django-common-helpers
• www/py-django-compat
• www/py-django-cron
• www/py-django-happenings-update
• www/py-django-sudo
• www/py-jsonfield2

[dvl]

Thank you

[bofh]

Thanks for the hard work. In case py-graphite-web is not updated to support support py-django32 before the removal of django22 please reap it. Will resurrect once it supports django32.

[koobs]

What is the impact on those remaining port without Django 3.2 support after this change lands?

What are the remaining steps (if any), post this change, to complete the migration?

[ultima]

Thanks for your work on this and the reminders that I needed to get things moving on seahub! =]

[kai]

In D34859#792390, @koobs wrote:

What is the impact on those remaining port without Django 3.2 support after this change lands?

Those ports keep assigned to Django 2.2 and still build fine once the other ports are switched to Django 3.2. The Django 2.2 ports expire on 2022-06-30 and should get removed before 2022Q3 lands.

What are the remaining steps (if any), post this change, to complete the migration?

Once this diff lands there are only three ports (which still build fine after this diff) we need to take care of:

• www/py-django-ldapdb (no new release yet, but it has already Django 3.2 compatible code, so I'm going to open a bug at FreeBSD's bugzill with a backport patch for it)
• www/py-django-modern-rpc (there's WIP for release 1.0.0 that has Django support, might be released during 2022Q2)
• www/py-django-tagging (there's already PR263216, but it has to wait until www/py-graphite-web gets updated or removed)