Current ones are deprecated now.

From v4 artifacts must have unique names or we get "Conflict: an
artifact with this name already exists on the workflow run".

It's been more than a year since Python 3.7 EOL.

Looks like we are not affected by changes in numpy.

macOS 11 support has been dropped.
Updating to macos-13 as latest standard image that is Intel MacOS.
Changing macos-13-xlarge to macos-14 as it is arm [1] and doesn't
require xlarge runner.

[1]
https://github.com/actions/runner-images?tab=readme-ov-file#available-images

Originally skbuild supplied its own test command which called "develop"
before calling original setuptools test command.

In order to avoid calling "develop", we directly exchanged this
skbuild.test command with setuptools.command.test.test

Note that in setup.py we only imported setuptools, not its submodules
like setuptools.command.test.
In skbuild they supply own version of test command to invoke and there
they imported setuptools.command.test. So we happened to use this import
indirectly.

In 0.18 release skbuild removed custom test command in [1].
As setuptools.command.test import went along with it, we started
getting errors like
module 'setuptools.command' has no attribute 'test'

Our use of setuptools.command.test.test might be remnant of the past
though.
By defining pytest as an alias of test and running python setup.py test,
we shouldn't have been running setuptools test at all. Also, setuptools
test seems to use unittest internally, which we don't do.

As test command is removed in setuptools 72.0.0 and reason for our own
override in setup.py is gone, we just drop the line altogether.

[1]scikit-build/scikit-build@dde5e79

Wheel is still build, even though it can't be tested. Looks like wheel
indication we used in cibuildwheel doesn't match the real wheel.

Original intent was not to build such wheels.

This is not the same as other workflows:
- core.yaml builds with python turned off
- wheels.yaml builds cpp core separately and then builds wheels
- docs.yaml uses python build system, but no tests
- bigendian.yaml is the one also doing tests, but it is slow and runs on
some oldish dependencies

So additional workflow is the best option to test python build.

Using setup.py to run commands is deprecated.
Currently remove test command only as it is explicitly deprecated.

pytest-runner was used to run pytests through setuptools, but now it is
no longer needed.

Python is in pre-release version, cibuildwheel already included it in
the matrix, but not all dependencies are yet in place (looks like numpy
wheels are not yet released for python 3.13).