As a HyperShift developer, I want a stable CI root cluster environment for Azure e2e tests, so that I can validate Azure HyperShift functionality continuously without infrastructure-related failures.

Context

The self-managed Azure HyperShift e2e tests need a reliable execution environment to validate functionality and prevent regressions. This story focuses on configuring the foundational cluster capabilities needed for test execution.

Acceptance criteria

• When e2e jobs are triggered, they should acquire capacity and start reliably on the root CI cluster
• When Azure credentials rotate, jobs should remain functional with updated secrets
• When failures occur, it should be possible to diagnose issues via logs and metrics from the root CI cluster
• When concurrency increases, the system should scale within budgeted quotas