chore(deps): update all dependencies

[renovate[bot]]

This PR contains the following updates:

Package	Type	Update	Change
github/codeql-action	action	patch	v2.22.9 -> v2.22.10
sigstore/cosign-installer	action	minor	v3.2.0 -> v3.3.0

---

Release Notes

github/codeql-action (github/codeql-action)

### [`v2.22.10`](https://togithub.com/github/codeql-action/compare/v2.22.9...v2.22.10) [Compare Source](https://togithub.com/github/codeql-action/compare/v2.22.9...v2.22.10)

sigstore/cosign-installer (sigstore/cosign-installer)

### [`v3.3.0`](https://togithub.com/sigstore/cosign-installer/releases/tag/v3.3.0) [Compare Source](https://togithub.com/sigstore/cosign-installer/compare/v3.2.0...v3.3.0) #### What's Changed - Bump actions/setup-go from 4.1.0 to 5.0.0 by [@​dependabot](https://togithub.com/dependabot) in [https://github.com/sigstore/cosign-installer/pull/152](https://togithub.com/sigstore/cosign-installer/pull/152) - update action to use latest cosign v2.2.2 by [@​cpanato](https://togithub.com/cpanato) in [https://github.com/sigstore/cosign-installer/pull/153](https://togithub.com/sigstore/cosign-installer/pull/153) **Full Changelog**: https://github.com/sigstore/cosign-installer/compare/v3.2.0...v3.3.0

---

Configuration

📅 Schedule: Branch creation - "after 10pm every weekday,before 5am every weekday,every weekend" in timezone Europe/Berlin, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• [ ] If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[sonarcloud[bot]]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

[github-actions[bot]]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.