[8.19] (backport #10160) Conditionally check for ms_tls13kdf build tag

[mergify]

What does this PR do?

This PR restores the check for the ms_tls13kdf Go build tag on the packaged FIPS-capable elastic-agent binary and component binaries. However, it only checks for this build tag if the binary was built with Go 1.24.x, which is where this tag was supported and required to ensure FIPS compliance.

Why is it important?

To ensure FIPS compliance of binaries built with Go 1.24.x.

Checklist

• I have read and understood the pull request guidelines of this project.
• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in ./changelog/fragments using the changelog tool
• I have added an integration test or an E2E test

Disruptive User Impact

None; this is a change to a Go test that gets executed when Elastic Agent is packaged.

How to test this PR locally

Create a FIPS-capable Elastic Agent package. Make sure a Go version other than 1.24.x is being used.

cat .go-version
FIPS=true SNAPSHOT=true EXTERNAL=true PLATFORMS="linux/arm64" PACKAGES="tar.gz" mage -v package

Make sure the package builds without any errors.

---

This is an automatic backport of pull request #10160 done by [Mergify](https://mergify.com).

[elasticmachine]

Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane)

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 0456ee0

Failed CI Steps

• Unit tests - Windows 2016

cc @ycombinator