chore(deps): update module github.com/cenkalti/backoff/v5 to v6

[red-hat-konflux]

This PR contains the following updates:

Package	Change	Age	Confidence
github.com/cenkalti/backoff/v5	v5.0.3 → v6.0.1

---

Warning

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

---

Release Notes

cenkalti/backoff (github.com/cenkalti/backoff/v5)

v6.0.1

Compare Source

v6.0.0

Compare Source

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• 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.

---

Documentation

Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: f9f9d701-5bfe-41fc-a1c4-aff1d43faa0f

📥 Commits

Reviewing files that changed from the base of the PR and between e028a14 and b47d9b9.

📒 Files selected for processing (1)

• go.mod

🔗 Linked repositories identified

CodeRabbit considers these linked repositories for cross-repo context during reviews:

• openshift/lightspeed-agentic-sandbox (manual)

✅ Files skipped from review due to trivial changes (1)

• go.mod

---

📝 Walkthrough

Summary by CodeRabbit

• Chores
  • Updated an indirect dependency to a newer major version, which may improve stability and compatibility behind the scenes.

Walkthrough

Updates the indirect Go module dependency github.com/cenkalti/backoff from major version v5 (v5.0.3) to major version v6 (v6.0.1) in go.mod.

Changes

Dependency bump

Layer / File(s)	Summary
cenkalti/backoff v5 → v6 go.mod	Indirect dependency github.com/cenkalti/backoff bumped from v5.0.3 to v6.0.1; this is a major version change.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the dependency upgrade from backoff v5 to v6.
Description check	✅ Passed	The description directly documents the same dependency update and its release notes.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

---

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@go.mod`:
- Line 48: The go.mod and go.sum files are out of sync for the
github.com/cenkalti/backoff module. While go.mod correctly specifies the v6
version of backoff, go.sum still contains stale entries from the previous v5
version. Run the command go mod tidy to reconcile and clean up the module files,
which will remove the outdated v5 entries from go.sum and ensure both files are
synchronized with the current v6 dependency specified in go.mod.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 9a5d288a-c45b-492e-8c80-d7eaf081272c

📥 Commits

Reviewing files that changed from the base of the PR and between d8d6698 and 0c88631.

📒 Files selected for processing (1)

• go.mod

🔗 Linked repositories identified

CodeRabbit considers these linked repositories for cross-repo context during reviews:

• openshift/lightspeed-agentic-sandbox (manual)

[openshift-merge-bot]

/retest-required

Remaining retests: 0 against base HEAD a18fcfb and 2 for PR HEAD 0c88631 in total

[openshift-merge-bot]

/retest-required

Remaining retests: 0 against base HEAD 106aa75 and 1 for PR HEAD 0c88631 in total

[openshift-merge-bot]

/retest-required

Remaining retests: 0 against base HEAD b34df3b and 0 for PR HEAD 0c88631 in total

[openshift-merge-bot]

/hold

Revision 0c88631 was retested 3 times: holding

[openshift-ci]

New changes are detected. LGTM label has been removed.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by:

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

The pull request process is described 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

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by:

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

The pull request process is described 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

[openshift-ci]

@red-hat-konflux[bot]: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/unit	b47d9b9	link	true	/test unit

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.