Upgrade Go dependency to next major version (1.19.x > 1.20.x)

[lukeheath]

Goal

User story
As an engineer,
I want to upgrade our Go dependency to the latest version
so that I can leverage the latest performance and security improvements for our users.

Changes

This issue's estimation includes completing:

• [ ] Evaluate the latest version of Go.
• [ ] Conduct risk-benefit analysis.
• [ ] Determine if/when we upgrade to the latest major and minor versions.

Context

• Requestor(s): Luke Heath

QA

Risk assessment

• [ ] Requires load testing TODO

Risk level: Low / High TODO

Risk description: TODO

Automated:

• Fleet: Cover / Will not cover
• QAWolf: Cover / Will not cover

Manual testing steps

1. Step 1
2. Step 2
3. Step 3

Testing notes

Confirmation

1. [ ] Engineer (@____): Added comment to user story confirming succesful completion of QA.
2. [ ] QA (@____): Added comment to user story confirming succesful completion of QA.

[lukeheath]

Per the check dependencies ritual, I am opening a new story to evaluate a major version upgrade of Go. This is not necessarily time sensitive, but we want to track this.

What do y'all think? If we recommend upgrading, I'll work with the product folks to move this through the drafting process so everyone is aware of the risks/rewards of the upgrade.

[lukeheath]

cc @zwass so this is on your radar

[lucasmrod]

Closing as stale as we are currently in Go 1.22.4.

[fleet-release]

Upgrade in the code, Performance, security grow, Fleet shines like cloud's abode.