fix/etcd flaky test

[aka1976mb]

The 'validateOlmAddon' integration test was using a custom retry loop
with 'retry.Expo' to check if the etcd operator's CSV had been
successfully installed. This could lead to intermittent failures (flakes)
in CI.

This change replaces the custom Go retry loop with a single, more
idiomatic 'kubectl wait' command. The command waits for the CSV's
status phase to become 'Succeeded', using 'kubectl''s built-in polling
mechanism.

This makes the test more robust and less prone to flakiness.

---

Fixes #22408

[linux-foundation-easycla]

• ❌ The email address for the commit (54b4026) is not linked to the GitHub account, preventing the EasyCLA check. Consult this Help Article and GitHub Help to resolve. (To view the commit's email address, add .patch at the end of this PR page's URL.) For further assistance with EasyCLA, please submit a support request ticket.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: aka1976mb
Once this PR has been reviewed and has the lgtm label, please assign prezha for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

Hi @aka1976mb. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[minikube-bot]

Can one of the admins verify this patch?