TestNG retries are marked as Skipped and the test itself is not marked as Flaky Test

[//]: # (
. Note: for support questions, please use Stackoverflow or Gitter**.
. This repository's issues are reserved for feature requests and bug reports.
.
. In case of any problems with Allure Jenkins plugin** please use the following repository
. to create an issue: https://github.com/jenkinsci/allure-plugin/issues
.
. Make sure you have a clear name for your issue. The name should start with a capital
. letter and no dot is required in the end of the sentence. An example of good issue names:
.
. - The report is broken in IE11
. - Add an ability to disable default plugins
. - Support emoji in test descriptions
)

#### I'm submitting a ...
- [X] bug report
- [ ] feature request
- [ ] support request => Please do not submit support request here, see note at the top of this template.

#### What is the current behavior?
Tests that failed and then success after re-run using TestNG retryAnalyzer marked as skipped and not showing the Flaky Test (bomb) icon.

#### If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
The retry impl class

public class RetryAnalyzerImpl implements IRetryAnalyzer {
private int maxRetryCount = 3;
private int retryCount = 0;

public boolean retry(ITestResult result) {
if (retryCount < maxRetryCount) {
retryCount++;
return true;
}
return false;
}
}

The test method

@Test(retryAnalyzer= RetryAnalyzerImpl.class)
public void VerifyRetrievePublicaAndActiveCommunity(){
int i = ThreadLocalRandom.current().nextInt(0, 2);
System.out.println(i);
Assert.assertEquals(i,0);
}

#### What is the expected behavior?
The retries are marked as Failed correctly. And the tests are marked as Flaky.

#### What is the motivation / use case for changing the behavior?

#### Please tell us about your environment:

| Allure version | 2.13.3 |
| Test framework | testng@7.1.0 |
| Allure integration | allure-testng@2.13.3 |
| Generate report using | allure windows cli@2.13.3 |

#### Other information

[//]: # (
. e.g. detailed explanation, stacktraces, related issues, suggestions
. how to fix, links for us to have more context, eg. Stackoverflow, Gitter etc
)

Commencez par reproduire le comportement avec le RetryAnalyzerImpl fourni et le test TestNG en utilisant allure-testng 2.13.3, puis suivez la manière dont les tentatives sont classées dans l’intégration TestNG et dans la sortie du rapport. Le travail est terminé lorsque les tentatives échouées ne sont pas signalées comme ignorées et que le test affiche l’indicateur Flaky Test.

Rédigé par le modèle d'indexation à partir du texte de l'issue.