chore: upgrade go to 1.25.7

[karel-rehor]

Required checklist

• Sample config files updated (both /etc folder and NewDemoConfig methods) (influxdb and plutonium) - N.A.
• openapi swagger.yml updated (if modified API) - link openapi PR - N.A.
• Signed CLA (if not already signed)

Description

Upgrades go to 1.25.7

Context

Need to resolve CVEs

1.25.6 and 1.24.12 were released to address:

• CVE-2025-61728 (archive/zip DoS)
• CVE-2025-61726 (net/http DoS)
• CVE-2025-68121 (crypto/tls; this had a regression)
• CVE-2025-61731 (cmd/go)
• CVE-2025-68119 (cmd/go)
• CVE-2025-61730 (crypto/tls)

1.25.7 and 1.24.13 were released to address

• CVE-2025-61732 (cmd/cgo)
• CVE-2025-68121 (crypto/tls; complete fix without regression)

Note for reviewers:

Check the semantic commit type:

• Feat: a feature with user-visible changes
• Fix: a bug fix that we might tell a user “upgrade to get this fix for your issue”
• Chore: version bumps, internal doc (e.g. README) changes, code comment updates, code formatting fixes… must not be user facing (except dependency version changes)
• Build: build script changes, CI config changes, build tool updates
• Refactor: non-user-visible refactoring
• Check the PR title: we should be able to put this as a one-liner in the release notes