py-cheetah3 and the semi-rename to CT3, textproc vs devel

[Greg Troxel <gdt%lexort.com@localhost>]

devel/py-cheetah3 is tracking an upstream on PyPI that is no longer
maintained.  You just can't make this up!

  https://cheetahtemplate.org/news.html

  3.3.0 (2022-10-10)

  Great move:

          PyPI has wrongfully classified project Cheetah3 as
          “critical”. This puts a burden to use 2FA to manage the project
          at PyPI. To avoid the burden the project is renamed to CT3 at
          PyPI. There will be no updates for Cheetah3. Sorry for the
          inconvenience!


I have wip/py-CT3 ready, and as plan A, I am inclined to import it to
textproc/py-CT3, because that's where a templating language belongs.
Then, things that depend on cheetah3 can be repointed.  Besides the name
change of the package, it's really just some normal updates.  Finally
py-cheetah3 can be removed.

As plan B, we would keep the py-cheetah3 package and just switch the upstream.
But it's renamed on pypi and thus our name and the PyPI name would not
match.

Overall, I perceive "upstream is keeping the cheetah3 name in all places
except PyPI" and thus plan B.

Any encouragement for B, contrary opinions or other views?