🐞: Selenium BiDi attachments land in the tearDown fixture, not the test result

### What happened?

When a WebDriver decorated with `AllureWebDriverBiDi` is closed via `driver.quit()` inside a JUnit 5 `@AfterEach`, the resulting "WebDriver BiDi network"/"WebDriver BiDi log" attachments are written to the `tearDown` fixture container instead of the test result itself.

### What Allure Integration are you using?

allure-selenium-bidi

### What version of Allure Integration you are using?

3.0-SNAPSHOT, commit 22cb1020

### What version of Allure Report you are using?

3.14.0

### Code of Conduct

- [x] I agree to follow this project's Code of Conduct

Start in the allure-selenium-bidi integration and reproduce the case with AllureWebDriverBiDi, JUnit 5, and driver.quit() inside @AfterEach. Check how the resulting "WebDriver BiDi network" and "WebDriver BiDi log" attachments are associated with the test result versus the tearDown fixture. Done means both attachments belong to the test result.

Written by the indexing model from the issue text.