Cucumber JSON reader: improve outlines support

Scenario outlines are reported differently across various cucumber JSON dialects. Some interpolate the example table name and the row number into the scenario's ID (Cucumber-Ruby, Cucumber-JS). Others - into the scenario's name (Behave).

We should carefully review different dialects and implement an algorithm to extract such IDs and convert them into the test's parameters or embed them into fullName to keep each test separated.

Review the Cucumber-Ruby, Cucumber-JS, and Behave JSON dialects described in the issue, focusing on how scenario-outline IDs and names encode example tables and rows. Trace the Cucumber JSON reader and determine whether extracted values should become test parameters or part of fullName; done means distinct tests remain separated across those dialects.

Written by the indexing model from the issue text.