🐞: update to 2.25.0 breaks working with Allure Testops for cucumber maven JUni4

[cheshi-mantu]

What happened?

when using 2.23

fullName: "DO: FMAAS-T9722 Check CF calculation when no value in cache"
{
  "name": "Parameter",
  "value": "Actual=PPPB Customer ID"
}
fullName: "DO: "DO: FMAAS-T9722 Checking CF calculation when no value in cache"
{
  }, "name": "parameter",
  "value": "Actual=PPRB Customer ID"
}
fullName: "DO: FMAAS-T9722 Check CF calculation when no value in cache" }
{
  }, "name": "parameter",
  "value": "Actual=dbo_EPC_ID of client"
}

when using 2.25

fullName: "src/test/resources/features/DO/tr-logic-dbo/FMAAS-T9722.feature:65"
{
  { "name": "parameter",
  "value": "Actual=PPPB Customer Identifier"
}
fullName: "src/test/resources/features/DO/tr-logic-dbo/FMAAS-T9722.feature:67"
{
  { "name": "parameter",
  "value": "fact=dbo_EPC_ID of client"
}
fullName: "src/test/resources/features/DO/tr-logic-dbo/FMAAS-T9722.feature:66"
{
  { "name": "parameter",
  "value": "Actual=PPRB Client Identifier"
}

Issue

fullName is now formed based on the FS path and reference to a line in feature file

for the same test with parameters we have now N different full names which breaks working with existing test cases in Allure Testops and does not allow correct creation of new test cases with parameters and creates N test cases instead of one with N parameters

What Allure Integration are you using?

allure-cucumber7-jvm

What version of Allure Integration you are using?

2.25.0

What version of Allure Report you are using?

2.25.0

Code of Conduct

• I agree to follow this project's Code of Conduct