devel/py-validate-pyproject: Update version requirement of BUILD_DEPENDS

devel/py-setuptools-scm: update to 8.0.4

Directory and PORTNAME changed to match normalised name in release
tarball; consumers updated to match.

Although setuptools itself is specified as a run dependency in the
Python package metadata, it is currently left out here to prevent
environment pollution until at least PR 270510 is committed.
Additionally, this version of setuptools-scm requires setuptools>=61,
which means this version is only meant for USE_PYTHON=pep517 ports
as all USE_PYTHON=distutils ports will switch to devel/py-setuptools58
also after PR 270510. science/py-emmet-core is switched to
devel/py-setuptools_scm7 accordingly, as it specifies setuptools-scm<8.
devel/py-{flit-scm,hatch-vcs} have ${PY_SETUPTOOLS} added to
RUN_DEPENDS to compensate.

Further details: https://wiki.freebsd.org/Python/setuptools

Reported by: yuri
Co-authored by: matthew
Exp-run by: antoine (earlier iteration)
Approved by: yuri (science/py-emmet-core, previous iteration)
PR: 272134
Differential Revision: https://reviews.freebsd.org/D39288

devel/py-validate-pyproject: Update to 0.16

Changes:	https://github.com/abravalheri/validate-pyproject/releases

devel/py-validate-pyproject: Update to 0.15

Changes:	https://github.com/abravalheri/validate-pyproject/releases

devel/py-validate-pyproject: Update to 0.14

Changes:	https://github.com/abravalheri/validate-pyproject/releases

devel/py-setuptools: convert individual consumers to ${PY_SETUPTOOLS}

Currently a no-op, but in the future outputs the correct setuptools
port depending on whether USES_PYTHON=distutils is specified.

With hat: python
PR: 270510, 270358

devel/py-validate-pyproject: Remove outdated PYTHON_REL check after
lang/python37 removal

all: remove explicit versions in USES=python for "3.x+"

The logic in USES=python will automatically convert this to 3.8+ by
itself.

Adjust two ports that only had Python 3.7 mentioned but build fine
on Python 3.8 too.

finance/quickfix: mark BROKEN with PYTHON

libtool: compile:  c++ -DHAVE_CONFIG_H -I. -I../.. -I -I. -I.. -I../.. -I../C++
-DLIBICONV_PLUG -DPYTHON_MAJOR_VERSION=3 -Wno-unused-variable
-Wno-maybe-uninitialized -O2 -pipe -DLIBICONV_PLUG -fstack-protector-strong
-fno-strict-aliasing -DLIBICONV_PLUG -Wall -ansi
-Wno-unused-command-line-argument -Wpointer-arith -Wwrite-strings
-Wno-overloaded-virtual -Wno-deprecated-declarations -Wno-deprecated -std=c++0x
-MT _quickfix_la-QuickfixPython.lo -MD -MP -MF
.deps/_quickfix_la-QuickfixPython.Tpo -c QuickfixPython.cpp  -fPIC -DPIC -o
.libs/_quickfix_la-QuickfixPython.o
warning: unknown warning option '-Wno-maybe-uninitialized'; did you mean
'-Wno-uninitialized'? [-Wunknown-warning-option]
QuickfixPython.cpp:175:11: fatal error: 'Python.h' file not found
          ^~~~~~~~~~
1 warning and 1 error generated.

Reviewed by:	portmgr, vishwin, yuri
Differential Revision:	<https://reviews.freebsd.org/D40568>

devel/py-validate-pyproject: Update to 0.13

Changes:	https://github.com/abravalheri/validate-pyproject/releases

devel/py-validate-pyproject: Update to 0.12.2

Changes:	https://github.com/abravalheri/validate-pyproject/releases

devel/py-validate-pyproject: Update to 0.12.1

Changes:	https://github.com/abravalheri/validate-pyproject/releases

USE_PYTHON=pep517: bump PORTREVISION

devel/py-validate-pyproject: Convert to USE_PYTHON=pep517

- Bump PORTREVISION for dependency and package change

*/*: rename CHEESESHOP to PYPI in MASTER_SITES

PR:			267994
Differential revision:	D37518
Approved by:		bapt

devel/py-validate-pyproject: Update to 0.10.1

Changes:	https://github.com/abravalheri/validate-pyproject/releases

Remove WWW entries moved into port Makefiles

Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.

This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.

Approved by:		portmgr (tcberner)

Add WWW entries to port Makefiles

It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.

Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.

There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.

devel/py-validate-pyproject: Update to 0.10

Changes:	https://github.com/abravalheri/validate-pyproject/releases

devel: remove 'Created by' lines

A big Thank You to the original contributors of these ports:

  *  "Waitman Gobble" <uzimac@da3m0n8t3r.com>
  *  <jkoshy@FreeBSD.org>
  *  Aaron Dalton <aaron@FreeBSD.org>
  *  Aaron Dalton <aaron@daltons.ca>
  *  Aaron H. K. Diep <ahkdiep@gmail.com>
  *  Aaron Hurt <ahurt@anbcs.com>
  *  Abel Chow <abel_chow@yahoo.com>
  *  Adam McLaurin
  *  Adam Saponara <as@php.net>
  *  Adam Weinberger <adamw@FreeBSD.org>
  *  Ade Lovett <ade@FreeBSD.org>

devel/py-validate-pyproject: Update to 0.9

Changes:	https://github.com/abravalheri/validate-pyproject/releases

devel/py-validate-pyproject: Update to 0.7.2

Changes:	https://github.com/abravalheri/validate-pyproject/releases

devel/py-validate-pyproject: Add py-validate-pyproject 0.7.1

With the approval of PEP 517 and PEP 518, the Python community shifted towards a
strong focus on standardisation for packaging software, which allows more
freedom when choosing tools during development and make sure packages created
using different technologies can interoperate without the need for custom
installation procedures.

This shift became even more clear when PEP 621 was also approved, as a
standardised way of specifying project metadata and dependencies.

validate-pyproject was born in this context, with the mission of validating
pyproject.toml files, and make sure they are compliant with the standards and
PEPs. Behind the scenes, validate-pyproject relies on JSON Schema files, which,
in turn, are also a standardised way of checking if a given data structure
complies with a certain specification.

WWW: https://github.com/abravalheri/validate-pyproject