allure-pytest 2.13.2 will merge parameterized use cases

#### Bug Description
When using @pytest.mark.parametrize() parametrization, the use cases are merged in the generated allure report, and it is not possible to generate an execution result record for each parametrized use case.

#### Steps to reproduce

#### Getting report results
The @pytest.mark.parametrize() parameterization executes four use cases, three of which pass and one of which fails, and sets the failing use case to retry once, and after the execution is complete, the generated allure report can only see the last report record, and the other use case executions are all categorized under " Retries" below

#### Expected Result
It is possible to display execution results for each use case individually, as in allure-pytest 2.13.1.

#### Running environment
- Allure version: 2.13.0
- Test framework: pytest 7.1.0
- Allure adaptor: allure-pytest 2.13.2

Commencez par reproduire le problème avec @pytest.mark.parametrize() en utilisant pytest 7.1.0 et allure-pytest 2.13.2, puis comparez le rapport généré avec celui d’allure-pytest 2.13.1. C’est terminé lorsque chaque cas d’utilisation paramétré possède son propre résultat d’exécution, y compris le cas en échec et sa nouvelle tentative, au lieu d’être regroupé sous Retries.

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