Better reporting for table driven scenarios.

[jensakejohansson]

Adds a suffix to the scenario name in the report indicating the index of the spec row, scenario row or both, that the scenario was executed with and the actual values used.

Part of getgauge/gauge#2790 and dependent on: getgauge/gauge#2798

Example of name with 'nested' table execution:

"Vowel counts in single word | SpecRow: 1: [word1: gauge] [count: 3] ScnRow: 1: [word2: g] [count2: 0]"

[gaugebot]

@jensakejohansson Thank you for contributing to xml-report. Your pull request has been labeled as a release candidate 🎉🎉.

Merging this PR will trigger a release.

Please bump up the version as part of this PR.

Instructions to bump the version can found at CONTRIBUTING.md

If the CONTRIBUTING.md file does not exist or does not include instructions about bumping up the version, please looks previous commits in git history to see what changes need to be done.

[jensakejohansson]

This was released too quickly! As stated in the description it's dependent on getgauge/gauge#2798 which is not yet released! I added 16.22 as Gauge minimum version in the commit! It's not yet released.

Problem is that Gauge doesn't seem to have decent logic to handle version dependencies. So if you have latest release Gauge 1.6.21 installed and do 'gauge install xml-report' it still installs xml-report 0.5.4 - which is not compatible!

[sriv]

gauge 1.6.22 is now released.