chore(ci): e2e report improve

[universal-itengineer]

Description

Improve the E2E messenger report generated by CI:

• add a Reason column to the failed-tests thread table;
• rename the failed-tests table column from Test group to Tests;
• link cluster names in failed-tests thread replies to the corresponding workflow/job URL;
• hide the Errors column in the main test-results table when there are no Ginkgo errors;
• calculate Success Rate from executed specs only: passed / (passed + failed + errors);
• add report table header emojis;
• use the full Ginkgo Failure.Message as the failed-test reason;
• avoid wrapping SSH command execution errors with %w so Ginkgo does not dump *exec.ExitError internals into the report;
• capture Ginkgo stdout/stderr as a fallback report source and surface suite-level failures such as SynchronizedBeforeSuite when the JSON report is missing or contains only setup failure data.

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

The current E2E notification thread only lists failed test groups and does not show why a test failed. This forces engineers to open CI artifacts/logs even for simple failures.

The report also displayed skipped specs as part of the success-rate denominator, which made Ginkgo success rate look worse than the actual executed-spec result. In addition, SSH command failures could include noisy Go internals in Failure.Message because *exec.ExitError was wrapped with %w.

When E2E fails in SynchronizedBeforeSuite, Ginkgo may skip all specs and the JSON report may be absent or contain no regular test failures. Previously the messenger report could only show a generic storage failure, for example nfs with E2E TEST FAILED, without the actual setup failure reason.

This change makes E2E notifications more actionable directly in the messenger thread and keeps the main summary easier to read.

What is the expected result?

1. Run the E2E report generation with a Ginkgo JSON report containing failed specs.
2. Check the main messenger report:
   • the Errors column is hidden when all error counts are zero;
   • Success Rate is calculated without skipped specs;
   • table headers include emojis.
3. Check the failed-tests thread:
   • cluster names are links;
   • the table has Tests and Reason columns;
   • Reason contains the Ginkgo Failure.Message text.
4. SSH command failures are rendered as useful text instead of dumping *exec.ExitError internals.
5. If Ginkgo fails in SynchronizedBeforeSuite and no JSON report is created, the report is still generated from the captured Ginkgo output and the failed-tests thread shows the suite-level failure reason. Suite-level failures do not change spec metrics such as passed, failed, errors, or total.

Checklist

• The code is covered by unit tests.
• e2e tests passed.
• Documentation updated according to the changes.
• Changes were tested in the Kubernetes cluster manually.

Changelog entries

section: ci
type: fix
summary: Improve E2E messenger report failure reasons, suite setup failure reporting, and success-rate calculation.
impact_level: low