update GH actions to change go version in go.mod file

[ntheanh201]

• Updated go version in go.mod file
• Updated GA to auto update the version in go.mod file whenever update Go version
• Tested: Update Go version to 1.23.4 ntheanh201/trafficcontrol#15

---

Which Traffic Control components are affected by this PR?

• Documentation
• Traffic Control Cache Config (t3c, formerly ORT)
• Traffic Control Health Client (tc-health-client)
• Traffic Control Client
• Traffic Monitor
• Traffic Ops
• Traffic Portal
• Traffic Router
• Traffic Stats
• Grove
• CDN in a Box
• Automation
• unknown

What is the best way to verify this PR?

If this is a bugfix, which Traffic Control versions contained the bug?

PR submission checklist

• This PR has tests
• This PR has documentation
• This PR has a CHANGELOG.md entry
• This PR DOES NOT FIX A SERIOUS SECURITY VULNERABILITY (see the Apache Software Foundation's security guidelines for details)

[zrhoffman]

Hmm, this will mean that a user cannot compile ATC using Go 1.23.3, and Go 1.23.4 or higher is required. Usually, minor versions are bugfixes and Go language changes are only introduced in major versions, so do we want to require specific minor versions?

[ntheanh201]

My reason is for aligning the Go version with .env and GO_VERSION is to maintain consistency across the development environment and avoid potential version mismatches.
I understand your perspective about not wanting to be overly restrictive with minor versions.
Would it better if we only watch & change the major/minor versions, and the patch keep 0?