[SYNTH-15675] Report timed out retries

[Drarig29]

What and why?

This PR fixes a bug where timed out retries were sometimes not reported.

Bug description:

• If a result (e.g. result ID 1) is an intermediate failed result (expected to be retried), its result ID is saved as reported,
• Now, if the retry times out, then the result ID is unchanged, resulting in datadog-ci thinking the result was already reported.

How?

In a backend PR, we added the max_retries property.

If the result is timed_out && retries < max_retries, then we report it as a residual result.

This PR also fixes the JUnit reporter by not saving intermediate results in the JUnit file, and adds a few properties (retries, max_retries, initial_result_id) to results in the JUnit file.

Review checklist

• [x] Feature or bugfix MUST have appropriate tests (unit, integration)

[datadog-datadog-prod-us1[bot]]

Datadog Report

Branch report: corentin.girard/SYNTH-15675/report-timed-out-retries Commit report: f5cb9bf Test service: datadog-ci-tests

:white_check_mark: 0 Failed, 1636 Passed, 0 Skipped, 1m 56.34s Total duration (1m 31.2s time saved)