Using @flaky or @muted or @known tags in Cucumber Scenarios or Feature doesn't reflect in Allure report

**Describe the bug**
Using @flaky or @muted or @known tags in Cucumber Scenarios or Feature doesn't reflect in Allure report. No markers were present in the report when using these tags.

**To Reproduce**
Steps to reproduce the behavior:
1. Create any cucumber feature file
2. Add flaky or muted or known tags to either scenario or feature
3. Observe the report markers

**Expected behavior**
When marked @flaky, scenario or feature should be marked as flaky and should able to filter using Markers in the allure report.

**Screenshots**
Please refer screenshot for expected behavior.

**Environment (please complete the following information):**

| Allure version | 2.17.3 |
| --- | --- |
| Test framework | testng@7.5 |
| Test framework | cucumber@7 |
| Allure adaptor | allure-cucumber7-jvm@2.17.3 |


@baev - please suggest any possible solution. Thanks!

Start by reproducing the issue with a Cucumber feature and @flaky, @muted, or @known tags using allure-cucumber7-jvm 2.17.3, TestNG 7.5, and Cucumber 7. Inspect the adapter and generated Allure results to trace where scenario or feature tags are handled. Done means the corresponding markers appear in the report and can be filtered.

Written by the indexing model from the issue text.