test(suites): Retire the Python suites, their driver and harness
Every suite the registry ran in Python has run beside its port (the
TypeScript and Rust suites of the previous commits) and printed the
same checks, so the registry names the ports and the Python goes:
108 files: the suites left in tests/e2e, tests/unit, tests/perf and
tests/image, their harness (helpers.py, core_lib.py, ts_static.py), the
Python tools of tests/tools, and the pytest driver (suites.py,
test_suites.py, conftest.py, pytest.ini, tests/requirements.txt).
What stays Python is what #552 kept there: the soak suites, which
drive pixelflux's and pcmflux's Python bindings and now share a harness
of their own (tests/soak/soak_lib.py, the standard library only; the
root window's size is read with xwininfo), the Jupyter entry point, the
two wheel-plan.py, the devcontainer's wheel selector, setup.py and the
examples.
- CI: the unit and suites jobs run
cargo xtask suiteson the pinned
toolchain and test the server the run's bundle carries, not a wheel
installed with pip (#547). Python is set up only where a tool is
Python's: the Jupyter suite's server and the soak tier. Playwright's
browsers come from the tests/ package, and a skipped suite fails the
run in the driver, not in a separate step. - The stall report the harness printed when a page stopped answering
(the host's load, every WebKit thread's state, CPU share and gdb
stack, kept in the work directory) is tests/lib/stall.ts, run when
the page-call bound gives up; CI keeps installing gdb for it. - The OSS scanner image runs the unit tier through the driver and no
longer installs pytest. - tests/README.md, AGENTS.md, the development guide and the devcontainer
describe the driver; references to retired files point at their
ports.