chore: upgrade to Go 1.22
Description
We've been testing against Go 1.22 for a few weeks now and things seem fine. This bumps the project to Go 1.22 as 1.21 becomes EOL in a few months.
Related Issues
Resolves #[issue_number]
How has this 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) -
Documentation -
Chore (Related to CI or Packaging to platforms) -
Test gap