chore: upgrade to go 1.22

[msvticket]

related to jenkins-x/jx#8670

[jenkins-x-bot]

[jx-info] Hi, we've detected that the pipelines in this repository are using a syntax that will soon be deprecated.
We'll continue to update you through PRs as we progress. Please check #8589 for further information.

[msvticket]

/retest

[msvticket]

/cc @tomhobson @JordanGoasdoue @garethjevans

[jenkins-x-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: garethjevans

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [garethjevans]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[vdemeester]

@msvticket @garethjevans any reason to use 1.22.3 over 1.22 ? This "kind-of" causes issues for projects depending on it but using go 1.22 as the version instead (like tektoncd/pipeline).

 go: github.com/jenkins-x/go-scm in vendor/modules.txt requires go >= 1.22.3 (running go 1.22.1) 

[msvticket]

@msvticket @garethjevans any reason to use 1.22.3 over 1.22 ? This "kind-of" causes issues for projects depending on it but using go 1.22 as the version instead (like tektoncd/pipeline).

 go: github.com/jenkins-x/go-scm in vendor/modules.txt requires go >= 1.22.3 (running go 1.22.1) 

In practice I think it was because Intellij set that automatically. But if it causes problems you can make a PR to change it.

[vdemeester]

In practice I think it was because Intellij set that automatically. But if it causes problems you can make a PR to change it.

Alright, perfect. I'll check something and will raise a PR if I can't get around it 🙃