Reporting for retries

[tim-yao]

Is your feature request related to a problem? Please describe.
Cucumber report(html, json formatter) doesn't include retried details when using --retry.

When we use --retry, report will mark the flaky test pass if there is one retry get pass. That is working as expected. However, if we can also add some details of retry in the report, e.g show the number of failed attempt, that will help us to find potential intermittent bugs, instead of hiding bugs.

The idea is coming from https://automationpanda.com/2021/06/14/are-automated-test-retries-good-or-bad/

Describe the solution you'd like
Something on the report to indicate there are retry attempts happened. Like the number of failed attempt. A example:

[luke-hill]

@SabotageAndi how do you do this in Specflow :D Care to offer a quick win :)

[aslakhellesoy]

We're not making any more changes to the JSON formatter, but this could be implemented in https://github.com/cucumber/common/tree/main/react/javascript#readme

Shall we move this issue to cucumber/common and tag it with react?

[aurelien-reeves]

I think the messages would have all the info for all messages-based formatters to be enhanced too

But first, let's focus on the html-formatter

[davidjgoss]

Noting here that @cucumber/query will likely need some new smarts to handle this. Currently it always gives you data from the last attempt of any given pickle or test case, but it'll need to be able to list attempts and get data for a given attempt.