chore(deps): update registry.access.redhat.com/ubi9/go-toolset docker tag to v9.7-1776084839

[red-hat-konflux]

This PR contains the following updates:

Package	Type	Update	Change
registry.access.redhat.com/ubi9/go-toolset	stage	patch	9.7-1774968108 → 9.7-1776084839
registry.access.redhat.com/ubi9/go-toolset	stage	major	1.25.8-1774968108 → 9.7-1776084839

---

Configuration

📅 Schedule: 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 these updates 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]

Walkthrough

Four Containerfiles were updated to change the base image version used for building bpfman-agent and bpfman-operator. The Go toolset versions in the build stages were incremented to a newer tag across both standard and OpenShift-specific variants.

Changes

Cohort / File(s)	Summary
bpfman-agent build images Containerfile.bpfman-agent, Containerfile.bpfman-agent.openshift	Updated build stage base image to registry.access.redhat.com/ubi9/go-toolset:9.7-1776084839 for Go toolchain compilation.
bpfman-operator build images Containerfile.bpfman-operator, Containerfile.bpfman-operator.openshift	Updated build stage base image to registry.access.redhat.com/ubi9/go-toolset:9.7-1776084839 for Go toolchain compilation.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

---

Important

Pre-merge checks failed

Please resolve all errors before merging. Addressing warnings is optional.

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Stable And Deterministic Test Names	❓ Inconclusive	Unable to retrieve PR change information due to missing git context and shell command execution limitations.	Provide the actual list of files modified in the PR or git diff output to determine if Ginkgo test files were changed.

✅ Passed checks (9 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: updating the registry.access.redhat.com/ubi9/go-toolset Docker base image tag across multiple Containerfiles.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Test Structure And Quality	✅ Passed	PR only updates Docker container image tags in Containerfile configurations with no test code modifications.
Microshift Test Compatibility	✅ Passed	PR only modifies Containerfile base image tags; no new Ginkgo e2e tests are added.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	PR contains only Containerfile dependency updates with no new Ginkgo e2e tests added, making SNO compatibility assessment not applicable.
Topology-Aware Scheduling Compatibility	✅ Passed	PR only modifies Containerfile base image tags; deployment manifests with existing tolerations are unchanged.
Ote Binary Stdout Contract	✅ Passed	PR only updates Docker base image tags in Containerfiles without modifying Go source code or binary stdout behavior.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	PR only updates Docker base image tags in Containerfiles; no Ginkgo e2e tests added, modified, or removed.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch konflux/mintmaker/main/registry.access.redhat.com-ubi9-go-toolset-9.x

---

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

[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.

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.

[frobware]

/approve
/lgtm
/ok-to-test

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: frobware, red-hat-konflux[bot]

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 [frobware]

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

[frobware]

/lgtm