Upgrade to go v1.22

[scr-oath]

• One step towards Upgrade to go version 1.23 to bring in iter.Seq and other language improvements #4101
• Is blocker for New Metrics: Open Telemetry #4065

[SyntaxNode]

There are also references to the Go version in:

• \Dockerfile
• .github\workflows\adapter-code-coverage.yaml
• .github\workflows\validate-merge.yaml
• .github\workflows\validate.yaml

[SyntaxNode]

We target to support the previous two Go releases. Therefore, please bump this up to only version 1.22.

[scr-oath]

How is the "supporting two releases" done by choosing an older version? Do you mean, instead, that you always stay on the "previous release"?

[scr-oath]

Not setting to 1.23 means that we can't start using the iter package yet, which can make some utilities that improve walking, say… []Bid (by walking the pointers to the Bid rather than making a copy of them for each iteration.

[scr-oath]

Here's an example file we can add to an iterators module in util

package iterators

import "iter"

// SlicePointers returns an iterator that yields indices and pointers to the elements of a slice.
func SlicePointers[Slice ~[]T, T any](s Slice) iter.Seq2[int, *T] {
	return func(yield func(int, *T) bool) {
		for i := range s {
			if !yield(i, &s[i]) {
				break
			}
		}
	}
}

// SlicePointerValues returns an iterator that yields pointers to the elements of a slice.
func SlicePointerValues[Slice ~[]T, T any](s Slice) iter.Seq[*T] {
	return func(yield func(*T) bool) {
		for i := range s {
			if !yield(&s[i]) {
				break
			}
		}
	}
}

And then use a la

		for seatBid := range iterators.SlicePointerValues(payload.BidResponse.SeatBid) {
			for bid := range iterators.SlicePointerValues(seatBid.Bid) {

[SyntaxNode]

How is the "supporting two releases" done by choosing an older version? Do you mean, instead, that you always stay on the "previous release"?

We build the Docker image using the latest version to take advantage of compiler / runtime improvements and restrict language features to the previous version.

Not setting to 1.23 means that we can't start using the iter package yet, which can make some utilities that improve walking, say… []Bid (by walking the pointers to the Bid rather than making a copy of them for each iteration.

Correct. We'll wait a little bit for those new features.

[bsardo]

Discussed offline with @SyntaxNode. Closing as we have since opened #4112.