Deduplicate junit reports for retried e2e specs
What does this MR do and why?
When e2e specs are retried in new process, results in junit and json report files need to be handled correctly to not create excess failure reporting.
junit
Add ability to merge junit reports and make sure report created by retry run uses different naming pattern so the various tooling that use it down the line, only read the initial run file
json
Do not save failures from original execution so that failure issue creators do not create issues for failures which passed on the retry
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Part of: gitlab-org/quality/quality-engineering/team-tasks#2268 (closed), gitlab-org/quality/quality-engineering/team-tasks#2590 (closed)