Stop running setup.py in our build+test infrastructure
Doing so is deprecated and also the source of some messiness. See these warnings when you test the Python SDK:
WARNING: Testing via this command is deprecated and will be removed in a future version. Users looking for a generic test entry point independent of test runner are encouraged to use tox. /home/brett/.cache/arvados-test/VENV3DIR/lib/python3.11/site-packages/setuptools/installer.py:27: SetuptoolsDeprecationWarning: setuptools.installer is deprecated. Requirements should be satisfied by a PEP 517 installer.
setup.py test we can use
python3 -m unittest.main, etc.
setup.py build we can use
python3 -m build, or there might be a direct setuptools invocation too (although it'll probably be deprecated soon if it's not already).
setup.py install we can use
python3 -m pip install.
This might be an epic, it might make sense to break out separate stories for individual parts like updating test infrastructure, updating build infrastructure, …