[Pavel Feldman (pavelfeldman)]

With --tracing/--video retain-on-failure or --screenshot only-on-failure, artifacts were discarded when a user fixture failed during teardown (e.g. a logged_in(page) fixture whose logout step raises). The recorder decided in its own fixture teardown, which runs before such failures are reported. Setup failures already kept artifacts.

• Videos are now copied out of Playwright in the fixture teardown, so everything that needs Playwright (and await in the asyncio plugin) still happens there. Under --video retain-on-failure this is one extra file copy per page for every test, passing ones included; before, passing tests only deleted the video.
• If the test has already failed, artifacts are kept right away, as before. Otherwise keeping or discarding them is deferred to pytest_runtest_makereport for the teardown report, which reflects failures from every fixture.
• A test skipped from a fixture (pytest.skip() during setup) no longer counts as failed. Before, retain-on-failure kept a test-failed-1.png and a trace for it.
• The pytest_runtest_makereport wrapper now runs trylast, so pytest_runtest_makereport hooks in conftest.py and in other plugins see the outcome it sets on the teardown report.
• The session temp folder is now cleaned up via config.add_cleanup, because the last test's teardown report comes after session fixtures are torn down.
• A filesystem error while moving deferred artifacts is reported as a teardown error of that test, not an INTERNALERROR that aborts the run. If a fixture already failed in teardown, its traceback stays the main one and the artifact error is added as a report section.

Tests: fixtures failing in setup and in teardown keep the screenshot, trace and video, a fixture that skips keeps nothing, and a failing shutil.move produces teardown errors with both messages (sync + async).

Fixes #117

_{Stack created with GitHub Stacks CLI • Give Feedback 💬}