[8.11] bump golang version 1.20.10

[leehinman]

What is the problem this PR solves?

Bump golang version to 1.20.10

How does this PR solve the problem?

// Explain HOW you solved the problem in your code. It is possible that during PR reviews this changes and then this section should be updated.

How to test this PR locally

Design Checklist

• I have ensured my design is stateless and will work when multiple fleet-server instances are behind a load balancer.
• I have or intend to scale test my changes, ensuring it will work reliably with 100K+ agents connected.
• I have included fail safe mechanisms to limit the load on fleet-server: rate limiting, circuit breakers, caching, load shedding, etc.

Checklist

• 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

Related issues

[elasticmachine]

💔 Build Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-11-14T19:28:35.027+0000

• Duration: 18 min 35 sec

Test stats 🧪

Test	Results
Failed	0
Passed	837
Skipped	1
Total	838

Steps errors

Expand to view the steps failures

test

• Took 2 min 19 sec . View more details here
• Description: make test-e2e

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[leehinman]

/test

[jlind23]

buildkite test this

[michel-laterman]

Please update the go version reference in the linter as well

[michel-laterman]

lgtm

[jlind23]

buildkite test this

[elastic-sonarqube]

SonarQube Quality Gate

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information