Bump the all-go-mod-patch-and-minor group with 8 updates

[dependabot]

Bumps the all-go-mod-patch-and-minor group with 8 updates:

Package	From	To
github.com/spyzhov/ajson	0.9.4	0.9.5
k8s.io/api	0.30.5	0.30.6
k8s.io/apimachinery	0.30.5	0.30.6
k8s.io/apiserver	0.30.5	0.30.6
k8s.io/client-go	0.30.5	0.30.6
k8s.io/code-generator	0.30.5	0.30.6
k8s.io/component-base	0.30.5	0.30.6
k8s.io/metrics	0.30.5	0.30.6

Updates github.com/spyzhov/ajson from 0.9.4 to 0.9.5

Release notes

Sourced from github.com/spyzhov/ajson's releases.

v0.9.5

Add is_*type* functions

Commits

• b7c6942 #67 Add is_*type* functions (#78)
• See full diff in compare view

Updates k8s.io/api from 0.30.5 to 0.30.6

Commits

• 9779f11 Update dependencies to v0.30.6 tag
• See full diff in compare view

Updates k8s.io/apimachinery from 0.30.5 to 0.30.6

Commits

• See full diff in compare view

Updates k8s.io/apiserver from 0.30.5 to 0.30.6

Commits

• 69cff1c Update dependencies to v0.30.6 tag
• 5fe3ee0 Merge pull request #126984 from dashpole/fix_mem_leak_30
• 0c59d42 update vendor
• 45413dc fix memory leak from global MeterProvider
• See full diff in compare view

Updates k8s.io/client-go from 0.30.5 to 0.30.6

Commits

• 24ad144 Update dependencies to v0.30.6 tag
• See full diff in compare view

Updates k8s.io/code-generator from 0.30.5 to 0.30.6

Commits

• d61b6e8 Update dependencies to v0.30.6 tag
• 304c199 Merge pull request #126984 from dashpole/fix_mem_leak_30
• d0ac547 Merge pull request #127307dims/automated-cherry-pick-of-#126353
• 3050aab run update-vendor.sh and fix up broken go.sum(s)
• a0d26b7 update vendor
• See full diff in compare view

Updates k8s.io/component-base from 0.30.5 to 0.30.6

Commits

• 2878576 Update dependencies to v0.30.6 tag
• See full diff in compare view

Updates k8s.io/metrics from 0.30.5 to 0.30.6

Commits

• 1f27b94 Update dependencies to v0.30.6 tag
• See full diff 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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

[zalando-robot]

Deployment Checklist

This change falls under our deployment policy. Would you call it low-risk? If so, please check this box:

• This is a low-risk change: a feature change or update behind a feature toggle, a minor change, a bug fix, or a patch. It is unlikely to disrupt services, or can be rolled back very quickly (feature toggle).

💁 If this is not a low-risk change, please confirm all of the following requirements:

• Detailed release notes are provided in this PR’s description.
• Thorough load-testing has been performed (link).
• Technical review: Principal Engineers or Tech Leads have green-lit your changes (link).
• You can enable/disable the change via feature toggles, and have confirmed these toggles work as expected.
• Management approval is given by … (Engineering Manager or above).

👉 Regardless of which boxes you click in this comment, merge/deployment will not be blocked (though it’ll be included in cyber week reporting).

[katyanna]

👍

[mikkeloscar]

👍