User Story:
As an OpenShift Engineer I want to ensure the upstream changes are present in the fork openshift/cloud-provider-aws so that we can test integrated feature with OCP components.

Description:
The downstream upgrade are usually updated per OCP release[1], although I asked Cloud team to run it more frequently in OCP 4.21 as we are depending of those updates to deliver the feature on time, and doing that we'll be able to validate it downstream quickly.

Note: this update can be done only when kube is updated to 1.34, which is tracked by the Slack channel https://redhat.enterprise.slack.com/archives/C096QTAL5JT 

Example of automated downstream update by CI step/bot https://github.com/openshift/cloud-provider-aws/pull/112 

[1] https://redhat-internal.slack.com/archives/CBZHF4DHC/p1756909808518969 

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