Phantom <lambda> teardown entries with unknown status when using pytest 9.1+

## Description

When using `allure-pytest` (2.15.3 or 2.16.0) with `pytest >= 9.1.0`, every fixture produces a phantom `::` afterStage entry in the Allure report with `unknown` status. These entries are not real teardown failures — they are internal pytest finalizers that allure wraps but are never invoked through allure's wrapper.

Versions
- pytest: 9.1.1
- allure-pytest: 2.16.0
- Python: 3.12
Works correctly with pytest <= 9.0.x.

Start by reproducing the report with allure-pytest 2.15.3 or 2.16.0 and pytest 9.1.1, then compare it with pytest 9.0.x. Trace the allure-pytest fixture teardown integration implicated by the issue; done means reports no longer contain phantom :: afterStage entries with unknown status.

Written by the indexing model from the issue text.