Remove expired ports:

2020-06-30 databases/p5-Search-Xapian10: Depend on unsupported xapian-core. Use
databases/p5-Search-Xapian instead
2020-06-30 databases/xapian-core10: Unsupported by upstream. Use
databases/xapian-core instead
2020-06-30 devel/py-dj22-django-rq: Obsolete, please use www/py-django-rq
instead
2020-06-30 devel/rubygem-cucumber-expressions: Use
devel/rubygem-cucumber-cucumber-expressions instead
2020-06-30 devel/rubygem-cucumber-expressions6: Use
devel/rubygem-cucumber-cucumber-expressions instead
2020-06-30 devel/rubygem-cucumber-tag_expressions1: Use
devel/rubygem-cucumber-tag_expressions instead
2020-06-30 print/xpp: Last update as 2004-12-09, unsupported by upstream
2020-06-30 textproc/rubygem-gherkin: Use textproc/rubygem-cucumber-gherkin
instead
2020-06-30 www/p5-Catalyst-Model-Xapian10: Depend on unsupported xapian-core.
Use www/p5-Catalyst-Model-Xapian instead
2020-06-30 www/py-dj22-django-auth-ldap: Obsolete, please use
www/py-django-auth-ldap instead
2020-06-30 www/py-dj22-django-cacheops: Obsolete, please use
www/py-django-cacheops instead
2020-06-30 www/py-dj22-django-cors-headers: Obsolete, please use
www/py-django-cors-headers instead
2020-06-30 www/py-dj22-django-crispy-forms: Obsolete, please use
www/py-django-crispy-forms instead

Set a few repo-copied py-dj22- ports to expire

* These ports were already set as DEPRECATED some time ago and now have no
  consumers left as those have been switched back to the original ports.

www/py-djangorestframework: Update to 3.11.0

* Switch the port to Django 2.2 (current LTS release) as well because
  Django 1.11 is End-of-Life since April.  Do the same for www/py-drf-yasg.

* Repo-copy www/py-djangorestframework to www/py-djangorestframework311
  which will be used as a transitional package by www/seahub until it gets
  support for Django 2.2+ in the next weeks/months.

* Drop the Python 2.7 support of the remaining consumers to avoid breakage
  of "bulk -a".

* Mark both repo-copied ports www/py-dj22-{djangorestframework,drf-yasg} as
  deprecated because they're obsolete now.

PR:		245309
Reviewed by:	sunpoet (earlier revision), ultima
Differential Revision:	https://reviews.freebsd.org/D24850

www/py-{dj21,dj22}-drf-yasg: Update to 1.17.0

Changelog:

https://github.com/axnsan12/drf-yasg/releases/tag/1.17.0

MFH:		2019Q4 (related to net-mgmt/netbox)

www/py-{dj21,dj22}-drf-yasg: Update to 1.16.1

This fixes also net-mgmt/netbox at runtime since r507098 [1]

Changelog:

* Fixed compatibility with Django REST framework 3.10.x [1]
* Improved enum type detection for nested "ChoiceFields"

https://github.com/axnsan12/drf-yasg/tree/1.16.1

PR:		240410
Submitted by:	Zane C. Bowers-Hadley <vvelox@vvelox.net>

www/py-{dj21,dj22}-drf-yasg: Update to 1.16.0

Changelog:

https://github.com/axnsan12/drf-yasg/blob/1.16.0/docs/changelog.rst

net-mgmt/netbox: Update to 2.5.12 and switch to Django 2.2

Upstream decided to switch from Django 2.1 to the 2.2 LTS release to fix a
rather annoying bug that generated intermittent errors when objects were
deleted/manipulated.

Therefore the same procedure must be done in almost the same way as in
r492690 to make NetBox compatible with Django 2.2 in the ports tree.

That means to repocopy the required Django 1.11 ports, assign them to
Django 2.2, limit them to Python 3.5+ and update all related
CONFLICTS_INSTALL entries accordingly:

* www/py-dj22-django-cors-headers [1]
* www/py-dj22-django-debug-toolbar