python.mk: retire ${PYNUMPY}

With both math/py-numpy (2) and math/py-numpy1, the variable stopped
making sense. Also remove the upper version bound.

math/py-numpy: switch all consumers to math/py-numpy1

...and bump PORTREVISIONs of consumers with hard RUN_DEPENDS

PR: 281470

science/py-dwave-preprocessing: update 0.6.10 → 0.6.11

Mk/Uses/python.mk: Remove USE_PYTHON=cython3{,_run,_test}

- Convert all cython3 occurrence to USE_PYTHON=cython*
- Bump PORTREVISION dependent ports of USE_PYTHON=cython_run for dependency
change

PR:		291778

science/py-dwave-preprocessing: update 0.6.6 → 0.6.10

python.mk: rename PYTHON_EXT_SUFFIX to PYTHON_TAG, document, etc

EXT_SUFFIX, according to PEP 3149, refers to the full tag and
extension for compiled extension module objects, eg .cpython-311.so,
.cpython-313t.so, etc. We do not use the correct semantic meaning,
and this usage becomes ambiguous and confusing when tags do not
match between bytecode and compiled extension module objects.

Rename our PYTHON_EXT_SUFFIX to PYTHON_TAG to align with PEP 3147's
specification of a magic tag, which consists of implementation name
and shorthand version only. This is meant for bytecode and other
files containing this tag in their filename that do not depend on
a specific Python ABI for the same version. Chase all existing
consumers.

Mk/Uses/python.mk: Introduce USE_PYTHON=cython3{,_run,_test}

- Update USE_PYTHON=cython{,_run,_test}
- Convert all cython3 occurrence to USE_PYTHON=cython3*
- While I'm here, fix incorrect usage of combining cython3 in BUILD_DEPENDS and
USE_PYTHON=cython

It is added to simplify the future transition from Cython 0.29 to 3.

The minimal version is set to 3.0.12 because it is required by
devel/py-propcache.
The upper bound of version is set to 3.1 because it is limited by multiple
ports.

python: bump all USE_PYTHON=distutils consumers after RUN_DEPENDS removal

Any missed ports, feel free to bump.

Any ports that need setuptools at runtime can have the devel/py-setuptools
manually added back to RUN_DEPENDS, but understand that this practice
is deprecated; see CHANGES for details.

science/py-dwave-preprocessing: update 0.6.5 → 0.6.6

Reported by:	portscout

science/py-dwave-preprocessing: update 0.6.3 → 0.6.5

Reported by:	portscout

science/{,py-}dwave-preprocessing: Update 0.6.2 → 0.6.3

Reported by:	portscout

science/py-dwave-preprocessing: Update 0.6.0 → 0.6.2

Reported by:	portscout

science/py-dwave-preprocessing: Update 0.5.4 → 0.6.0

Reported by:	portscout

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>

*: Bump PORTREVISIONs for math/mpc update to 1.3.1

science/py-dwave-preprocessing: Update 0.5.2 -> 0.5.4

Reported by:	portscout

science/py-dwave-preprocessing: Update 0.4.0 -> 0.5.2

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.

science/py-dwave-preprocessing: Fix conflict with other package

science/py-dwave-preprocessing: New port: DWave: Preprocessing tools to aid in
solving binary quadratic models