[main][gomod]: Bump github.com/go-logr/logr from 1.4.3 to 1.4.4 in the patch group across 1 directory

[dependabot]

Bumps the patch group with 1 update in the / directory: github.com/go-logr/logr.

Updates github.com/go-logr/logr from 1.4.3 to 1.4.4

Release notes

Sourced from github.com/go-logr/logr's releases.

v1.4.4

What's Changed

• drop +build tags by @​pohly in go-logr/logr#401
• CI: avoid floating dependencies, fix issues by @​pohly in go-logr/logr#432
• Bump to Go 1.26 by @​thockin in go-logr/logr#445
• funcr: bound slog.Group nesting depth to prevent stack overflow by @​martinholovsky in go-logr/logr#447
• funcr: Handle and test recursive values by @​thockin in go-logr/logr#446

New Contributors

• @​martinholovsky made their first contribution in go-logr/logr#447

Full Changelog: go-logr/logr@v1.4.3...v1.4.4

Commits

• 96a9aba Fix lint
• 51c6302 Better implementation of pointer recursion checking
• c667114 funcr: Handle and test recursive values
• f7ffadb Add benchmark for pointer args
• e2a3c8e funcr: bound slog.Group nesting depth to prevent stack overflow
• 2886d2b build(deps): bump actions/setup-go from 6.5.0 to 7.0.0
• 0b40896 build(deps): bump github/codeql-action/upload-sarif
• 77f671b Bump to Go 1.26
• cce283f build(deps): bump golangci/golangci-lint-action from 9.2.1 to 9.3.0
• 3832a11 build(deps): bump github/codeql-action/upload-sarif
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dependabot[bot]
Once this PR has been reviewed and has the lgtm label, please assign creydr 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 @dependabot[bot]. Thanks for your PR.

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