chore: fix vulnerabilities inside indirect deps

[afdesk]

Description

This PR depends on #2953 and updates indirect dependencies to fix vulnerabilities inside them.

Before:

% trivy i -q aquasec/trivy-operator:0.30.1

Report Summary

┌───────────────────────────────────────────────┬──────────┬─────────────────┬─────────┐
│                    Target                     │   Type   │ Vulnerabilities │ Secrets │
├───────────────────────────────────────────────┼──────────┼─────────────────┼─────────┤
│ aquasec/trivy-operator:0.30.1 (alpine 3.23.3) │  alpine  │       18        │    -    │
├───────────────────────────────────────────────┼──────────┼─────────────────┼─────────┤
│ usr/local/bin/trivy-operator                  │ gobinary │       34        │    -    │
└───────────────────────────────────────────────┴──────────┴─────────────────┴─────────┘
...

aquasec/trivy-operator:0.30.1 (alpine 3.23.3)

Total: 18 (UNKNOWN: 0, LOW: 0, MEDIUM: 6, HIGH: 10, CRITICAL: 2)
...

usr/local/bin/trivy-operator (gobinary)

Total: 34 (UNKNOWN: 0, LOW: 1, MEDIUM: 15, HIGH: 17, CRITICAL: 1)

After:

 % trivy i -q  docker.io/afdesk/trivy-operator:vulns-2026-05-14

Report Summary

┌──────────────────────────────────────────────────────────────────┬──────────┬─────────────────┬─────────┐
│                              Target                              │   Type   │ Vulnerabilities │ Secrets │
├──────────────────────────────────────────────────────────────────┼──────────┼─────────────────┼─────────┤
│ docker.io/afdesk/trivy-operator:vulns-2026-05-14 (alpine 3.23.3) │  alpine  │        0        │    -    │
├──────────────────────────────────────────────────────────────────┼──────────┼─────────────────┼─────────┤
│ usr/local/bin/trivy-operator                                     │ gobinary │        0        │    -    │
└──────────────────────────────────────────────────────────────────┴──────────┴─────────────────┴─────────┘

Checklist

• I've read the guidelines for contributing to this repository.
• I've added tests that prove my fix is effective or that my feature works.
• I've updated the documentation with the relevant information (if needed).
• I've added usage information (if the PR introduces new options)
• I've included a "before" and "after" example to the description (if the PR is a user interface change).