Flaky test statictics for prioritization

**Is your feature request related to a problem? Please describe.**
Our project is developed by 30+ people. We use trunk-based development with feature branching. Before merging branch into master gitlab CI executing automatic tests.
Some tests are flaky and we want to prioritize it to plan work and solve problem.

**Describe the solution you'd like**
Every test report is copied to allure folder and allure shows statistics with cases order by flaky frequency.

**Describe alternatives you've considered**
Maybe, a service for gitlab CI, which parse every job.

**Additional context**
Filter by branch name may be also useful to distinguish error tests from dev work.

The issue names Allure reports, the Allure folder, and GitLab CI jobs, but no files, tests, or entry points. Start by reviewing how existing Allure statistics are generated and how CI test reports are collected. Done should include flaky-frequency ordering and, if in scope, branch-name filtering.

Written by the indexing model from the issue text.