test(ci): rename ginkgo json report file

[universal-itengineer]

Description

Fix E2E report handling in the reusable CI pipeline. The workflow now keeps the raw Ginkgo JSON report separate from the generated summary report and validates the loaded report before using it to build the final E2E status artifact.

Why do we need it, and what problem does it solve?

The pipeline started producing two JSON files for E2E runs: a summary object and a raw Ginkgo report array. Both matched the e2e_summary_*.json pattern, so the failure-report step could pick the wrong file and then crash in jq when it tried to read array data as a summary object.

What is the expected result?

The reusable E2E workflow consistently picks the summary JSON for downstream processing, keeps the raw Ginkgo report available as an artifact under a separate name, and no longer fails in the reporting step when both files are present.

Changelog entries

section: ci
type: fix
summary: Prevent E2E report parsing failures by separating the raw Ginkgo JSON report from the summary report in CI artifacts.
impact_level: low