fix(deps): update module github.com/bpfman/bpfman-operator to v0.5.6

[red-hat-konflux]

This PR contains the following updates:

Package	Type	Update	Change
github.com/bpfman/bpfman-operator	require	patch	v0.5.5 -> v0.5.6

---

Release Notes

bpfman/bpfman-operator (github.com/bpfman/bpfman-operator)

v0.5.6

Compare Source

The v0.5.6 release is a patch release. The primary reason for the release is to move the version of sigstore-rs because of a breaking change which caused all previous bpfman versions to no longer be able to verify images. The CSI driver container used by bpfman-operator was also updated to support multiple architectures.

What's Changed

• post v0.5.5 cleanup by @​Billy99 in https://github.com/bpfman/bpfman-operator/pull/360
• update golang to 1.23 and build crictl from source by @​msherif1234 in https://github.com/bpfman/bpfman-operator/pull/362
• ci: upgrade upload-artifact action to v4 in scorecard workflow by @​frobware in https://github.com/bpfman/bpfman-operator/pull/367
• update csi-node-driver-registrar container for multiarch by @​Billy99 in https://github.com/bpfman/bpfman-operator/pull/370
• docs: move bpfman-operator details from README to docs by @​Billy99 in https://github.com/bpfman/bpfman-operator/pull/366
• Add "patch" to verbs for namespace-scoped CRDs in namespace_scoped.yaml by @​anfredette in https://github.com/bpfman/bpfman-operator/pull/372
• Fix random failures in unit tests by @​anfredette in https://github.com/bpfman/bpfman-operator/pull/371
• Add license scan report and status by @​fossabot in https://github.com/bpfman/bpfman-operator/pull/374

Full Changelog: bpfman/bpfman-operator@v0.5.5...v0.5.6

New Contributors

• @​fossabot made their first contribution in https://github.com/bpfman/bpfman-operator/pull/374

---

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

[red-hat-konflux]

ℹ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

• 15 additional dependencies were updated

Details:

Package	Change
github.com/prometheus/common	v0.55.0 -> v0.57.0
k8s.io/api	v0.32.1 -> v0.32.2
k8s.io/apimachinery	v0.32.1 -> v0.32.2
k8s.io/client-go	v0.32.1 -> v0.32.2
sigs.k8s.io/controller-runtime	v0.20.1 -> v0.20.2
cel.dev/expr	v0.18.0 -> v0.19.0
github.com/evanphx/json-patch/v5	v5.9.0 -> v5.9.11
golang.org/x/crypto	v0.31.0 -> v0.32.0
golang.org/x/net	v0.33.0 -> v0.34.0
golang.org/x/oauth2	v0.24.0 -> v0.25.0
golang.org/x/sys	v0.28.0 -> v0.29.0
golang.org/x/term	v0.27.0 -> v0.28.0
google.golang.org/genproto/googleapis/rpc	v0.0.0-20241209162323-e6fa225c2576 -> v0.0.0-20250102185135-69823020774d
google.golang.org/grpc	v1.68.1 -> v1.70.0
google.golang.org/protobuf	v1.36.1 -> v1.36.5

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign eranra 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

[openshift-ci]

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

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

[openshift-merge-robot]

PR needs rebase.

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.