chore(dependency): Upgrade to golang 1.24.4

[PeterSchafer]

Pull Request Submission Checklist

• Follows CONTRIBUTING guidelines
• Commit messages
  are release-note ready, emphasizing
  what was changed, not how.
• Includes detailed description of changes
• Contains risk assessment (Low | Medium | High)
• Highlights breaking API changes (if applicable)
• Links to automated tests covering new functionality
• Includes manual testing instructions (if necessary)
• Updates relevant GitBook documentation (PR link: ___)
• Includes product update to be announced in the next stable release notes

What does this PR do?

This PR updates golang from 1.23 to 1.24 and adapt to the new FIPS related aspects.

1. Updated how FIPS is enabled chore: upgrade to go 1.24 go-application-framework#391
2. Update golang version build image
3. Updated e2e test image to use an image that has fips enabled by default

Where should the reviewer start?

How should this be manually tested?

What's the product update that needs to be communicated to CLI users?

[snyk-io]

🎉 Snyk checks have passed. No issues have been found so far.

✅ security/snyk check is complete. No issues have been found. (View Details)

✅ license/snyk check is complete. No issues have been found. (View Details)

✅ code/snyk check is complete. No issues have been found. (View Details)

[github-actions]

Your PR has not had any activity for 30 days. In 2 days I'll close it. Make some activity to remove this.

[PeterSchafer]

This is required during building the build image.

[github-actions]

	Warnings
⚠️	There are multiple commits on your branch, please squash them locally before merging!

Generated by 🚫 dangerJS against 0f6394b