GeezerVison

Fixes #1453

Problem

When Selenide executes nested steps (for instance, a custom high-level test step wrapping an element action or assertion), failure in an inner step triggers �fterEvent with EventStatus.FAIL for both the inner step and all enclosing steps during step commit. Previously, this caused duplicate screenshot and page source attachments to be added across every enclosing step for the exact same failure.

Solution

• Track captured Throwable instances in AllureSelenide using a WeakHashMap-backed set.
• In �fterEvent, check the failure throwable and its cause hierarchy (getCause()) against previously recorded failures before capturing screenshots and page source attachments.
• Enclosing steps encountering the same failure instance or wrapped cause do not create duplicate attachments.
• Distinct failures across steps continue to capture attachments normally.
• Unit tests added covering nested step deduplication, wrapped cause deduplication, and distinct failure attachment retention.