Install: use setuptools bdist_wheel; CI: call pytest as module

[ipanfilo]

Description

Compatibility changes for python 3.14 images

Type of change

• Documentation change (change only to the documentation, either a fix or a new content)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Infra/Build change
• Code refactoring

Changes

• Use setuptools bdist_wheel since wheel one is deprecated
• Call python -m pytest instead of pytest in CI to fix incorrect python running on images with multiple pythons

Checklist:

• I have read and followed the contributing guidelines
• The functionality is complete
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[matthiasdiener]

In line 237 above, we run python, not python3, perhaps we could also use python here? (perhaps it would also make sense to additionally run which python above to log which actual python binary is used)

Suggested change

	python3 -m pytest -v -rfEs `get_pytest_junitxml $_test_name_tag` $TEST_PYTEST_ARGS "$TEST_DIR/$@"
	python -m pytest -v -rfEs `get_pytest_junitxml $_test_name_tag` $TEST_PYTEST_ARGS "$TEST_DIR/$@"

[ipanfilo]

I changed line 237 to python3 because it is recommended way to run it.