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

Start by reproducing the issue with @pytest.mark.parametrize() using pytest 7.1.0 and allure-pytest 2.13.2, then compare the generated report with allure-pytest 2.13.1. Done means each parametrized use case has its own execution result, including the failed case and its retry, rather than being merged under Retries.

Written by the indexing model from the issue text.