[TT-13428] Upgrading Go to v1.22.7

[mativm02]

Description

In order to get rid of a reported CVE that's present in Go versions lower than v1.22.7, we need to update it.

Slack thread: https://tyktech.slack.com/archives/C029UHHJ03T/p1729772954993819
CVE link: https://scout.docker.com/vulnerabilities/id/CVE-2024-34158?s=golang&n=stdlib&t=golang&vr=%3C1.22.7&utm_source=desktop&utm_medium=ExternalLink

Related Issue

https://tyktech.atlassian.net/browse/TT-13428?atlOrigin=eyJpIjoiNzJhYzM3OTA5ZDRiNDM2Njg2MWZjMWE0OGMwMmQwYTkiLCJwIjoiaiJ9

Motivation and Context

https://tyktech.atlassian.net/browse/TT-13428?atlOrigin=eyJpIjoiNzJhYzM3OTA5ZDRiNDM2Njg2MWZjMWE0OGMwMmQwYTkiLCJwIjoiaiJ9

How This Has Been Tested

Screenshots (if appropriate)

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• Make sure you are requesting to pull a topic/feature/bugfix branch (right side). If pulling from your own
  fork, don't request your master!
• Make sure you are making a pull request against the master branch (left side). Also, you should start
  your branch off our latest master.
• My change requires a change to the documentation.
  • If you've changed APIs, describe what needs to be updated in the documentation.
• I have updated the documentation accordingly.
• Modules and vendor dependencies have been updated; run go mod tidy && go mod vendor
• I have added tests to cover my changes.
• All new and existing tests passed.
• Check your code additions will not fail linting checks:
  • go fmt -s
  • go vet