Improvement: Unify and Refactor Screenshot Logic

[oomelianchuk]

Summary

Currently, we have screenshots per step, screenshots on error and screenshots on success logic defined in different places. This makes it hard to maintain. Please, unify the logic to make this part of the framework more maintainable.

Suggestion

See if we can use Allure Lifecycle Listeners to handle all screenshots at the same point. Use AllureTestStepListener and AllureTestStepListener as references