User Story:

As an OpenShift Engineer I want to increase verbosity/data gathering when e2e job fails on CCM-AWS repository, so that devs can troubleshoot easier and go quickly to the controller failure, enhancing current e2e framework that isn't collecting enough controller information.

Ref <https://github.com/kubernetes/cloud-provider-aws/pull/1214#issuecomment-3115210021>.

Description:

There are several changes added to the PR[1] that proposes to increase verbosity and help to troubleshoot CCM/service failures on CI e2e jobs. 

The main goal of this task is to isolate this change in a dedicated PR to be used in other PRs while[1] isn't merged (which may take long as it is blocked for permissinos changes)

[1]  Example of improvements by high verbosity on e2e:

https://github.com/kubernetes/cloud-provider-aws/pull/1214/files#diff-05b1c14f2de829d8a0c5f65b1b492a9ed9ab9d100ce6daa89d2d2347c8a14c77R309-R969 

https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/pull/cloud-provider-aws/1214/pull-cloud-provider-aws-e2e/1948477553773645824#1:build-log.txt%3A2155 

Acceptance Criteria:
< Record how we'll know we're done >

Other Information:
< Record anything else that may be helpful to someone else picking up the card >

issue created by splat-bot

created from thread: https://redhat-internal.slack.com/archives/G012C6LKVM2/p1753397993147999