chore(deps): update module github.com/avast/retry-go/v4 to v4.6.1

[red-hat-konflux]

This PR contains the following updates:

Package	Change	Age	Confidence
github.com/avast/retry-go/v4	v4.5.1 -> v4.6.1

---

Warning

Some dependencies could not be looked up. Check the warning logs for more information.

---

Release Notes

avast/retry-go (github.com/avast/retry-go/v4)

v4.6.1

Compare Source

What's Changed

• Update link to docs by @​ajeetdsouza in #​100
• fix test for slow windows + add newer golang versions by @​JaSei in #​126
• Bump github.com/stretchr/testify from 1.9.0 to 1.10.0 by @​dependabot in #​123
• Make sure DelayType function gets consistent values of n by @​haaawk in #​125

New Contributors

• @​ajeetdsouza made their first contribution in #​100
• @​haaawk made their first contribution in #​125

Full Changelog: avast/retry-go@4.6.0...v4.6.1

v4.6.0

Compare Source

What's Changed

• Introduce UntilSucceeded option to improve readability by @​natenho in #​116
• Fix the inconsistency in the number of times passed in onRetry by @​FarmerChillax in #​114
• Bump github.com/stretchr/testify from 1.8.4 to 1.9.0 by @​dependabot in #​112

New Contributors

• @​natenho made their first contribution in #​116
• @​FarmerChillax made their first contribution in #​114

Full Changelog: avast/retry-go@v4.5.1...v4.6.0

---

Configuration

📅 Schedule: Branch creation - "after 5am on sunday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

To execute skipped test pipelines write comment /ok-to-test.

This PR has been generated by MintMaker (powered by Renovate Bot).

[openshift-ci]

Hi @red-hat-konflux[bot]. Thanks for your PR.

I'm waiting for a openshift 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.

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.