Enhance Report Portal with Component Version Tracking and Failure Logs

## Summary
Improve Report Portal integration to automatically capture and report component versions, container image SHAs, and component logs when tests fail.

## Problem
Currently our Report Portal lacks environment context - we don't know which versions of Kuadrant operator, Authorino, Limitador were tested, and when tests fail we have to manually gather component logs for debugging.

## Solution
- Automatically detect and report component versions and image SHAs as test attributes
- Capture relevant component logs and attach them to failed test reports
- Add structured metadata for better test environment tracking and failure analysis

## Benefits
Faster debugging with immediate access to logs and versions, better environment reproducibility, and automated failure diagnostics without manual investigation.

The issue names no files, tests, or entry points. Start by locating the Report Portal integration and the existing test-result metadata and failure-log handling, then trace how component versions and logs are available. Done means failed reports include the requested versions, image SHAs, logs, and structured environment metadata.

Written by the indexing model from the issue text.