Exporting feature files from a Requirement, Test Set, Test Plan and Test Execution issues, places a tag of the Test Set key on the Scenario that will be imported as a label to the Test issue

Short Description: Exporting feature files from a Requirement, Test Set, Test Plan and Test Execution issues, places a tag of the Test Set key on the Scenario that will be imported as a label to the Test issue. If the user exports the file again, then another tag is placed, duplicating the same tag and also duplicating the same label if imported again and so on.

Steps to Reproduce:

1 - Create a cucumber Test and added it to a Test Set.

2 - Navigate to the Test Set issue and export the feature to cucumber.

3 - Open the file. It is possible to see a tag of the Test Set key in the scenario.

4 - Import that file. The Test is updated with a label which is the Test Set key.

5 - Go to the Test Set and export the feature again.

6 - In the file is now visible two equal tags (a second one from the second export).

7 - Import the file. The Test is updated and another label is placed.

Expected Results: Please check with P.O. what exactly should be the behaviour here. Should we export the Test Set key as a tag in the first place? Seems to happen only for the Test Set. If it should be exported should we ignore it when importing the file? Should this be used to link the Test to a Test Set in case it is a new issue key?