allure 和 pytest.mark 不应该混淆

[//]: # (
. 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?
不应该出现的标签

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

@allure.link("https://www.baidu.com/", name="baidu")
@allure.issue("https://www.baidu.com/", "BUG")
@allure.testcase("YHZ-123")
@pytest.mark.repeat(1)
@pytest.mark.parametrize("coupons_type", [1, 2])
def xxx():
pass


#### What is the expected behavior?
预期结果，allure 和 pytest.mark 不应该 混淆

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

#### Please tell us about your environment:

Python = 3.9.0
allure = 2.17.2
allure-pytest = 2.13.2

#### Other information

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

Inizia riproducendo il comportamento segnalato con lo snippet di codice del decorator fornito nell’ambiente indicato con Python 3.9.0, allure 2.17.2 e allure-pytest 2.13.2. Esamina il punto di ingresso dell’integrazione allure-pytest responsabile dell’elaborazione dei marker di pytest, confronta le label generate con lo screenshot allegato e il comportamento previsto, quindi aggiungi un test di regressione una volta confermato il risultato previsto.

Scritto dal modello di indicizzazione a partire dal testo della issue.