Bump Go toolchain and dependencies to resolve security vulnerabilities

[chrcha1]

Description

Problem

The retina-agent image built from dev/v0.0.33-windows is flagged by container image vulnerability scanning known Go CVEs (stdlib plus modules such as containerd, grpc, golang.org/x/net, mapstructure/v2, runc and aws-sdk-go-v2)

Since branch dev/v0.0.33-windows was created from commit 82d621c (May 2025, ~500 commits behind), so Go toolchain/dependencies are frozen. main is already patched, so we are fixing staleness.

Aligned the branch's Go toolchain and dependencies with the patched versions main already uses:

• Go builder mcr.microsoft.com/oss/go/microsoft/golang 1.24.x -> 1.26.5 across the controller/operator/cli/test Dockerfiles (Linux azurelinux3.0, Windows windowsservercore-ltsc2022; operator-windows moves cbl-mariner2.0 -> azurelinux3.0 since there's no 1.26 Mariner tag). Building with 1.26.5 clears the stdlib advisories (the scanner reads the Go version baked into the binary).
• go directive 1.24.3 -> 1.26.0.
• mapstructure/v2 -> 2.5.0, containerd -> 1.7.33, runc -> 1.2.8 + selinux -> 1.13.1, grpc -> 1.79.3, golang.org/x/net -> 0.57.0, aws-sdk-go-v2/.../eventstream -> 1.7.14, docker/docker -> 28.5.2.

note
left out cilium, inspektor-gadget, and docker as their patched versions dropped/moved the exact packages we import (or the fix lives in a totally different module), so bumping them breaks the build and needs the code refactors main  already did (everything else was a clean version bump)

Related Issue

If this pull request is related to any issue, please mention it here. Additionally, make sure that the issue is assigned to you before submitting this pull request.

Checklist

• I have read the contributing documentation.
• I signed and signed-off the commits (git commit -S -s ...). See this documentation on signing commits.
• I have correctly attributed the author(s) of the code.
• I have tested the changes locally.
• I have followed the project's style guidelines.
• I have updated the documentation, if necessary.
• I have added tests, if applicable.

Screenshots (if applicable) or Testing Completed

Please add any relevant screenshots or GIFs to showcase the changes made.

Additional Notes

Add any additional notes or context about the pull request here.

---

Please refer to the CONTRIBUTING.md file for more information on how to contribute to this project.

[chrcha1]

@chrcha1 please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@microsoft-github-policy-service agree [company="{your company}"]

Options:

• (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

• (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

@microsoft-github-policy-service agree company="Microsoft"