ci(buildkit): match moby go version for buildkit tests

[crazy-max]

follow-up

• [0.11 backport] hack: allow to set GO_VERSION during tests buildkit#4018
• [0.11] Dockerfile: missing GO_VERSION arg buildkit#4019

related to

• ci(bin-image): fix meta step #45932 (comment)
• Golang client fails to attach to streams with "http: invalid Host header" with go1.20.6, go1.19.11 #45935

- What I did

BuildKit integration tests image always pulls latest Go 1.20: https://github.com/moby/buildkit/blob/ca5d5bff71976d99d3ae6bb55dae7e4dd017c22d/Dockerfile#L19

With latest Go 1.20.6 we see failed tests in buildkit workflow (#45932 (comment)) related to #45935

Let's pin go version for buildkit tests matching the one in this repo.

- How I did it

- How to verify it

- Description for the changelog

- A picture of a cute animal (not mandatory but encouraged)

[crazy-max]

@thaJeztah As discussed we still need to vendor back to BuildKit v0.11 the 23.0 branch once #45942 is merged with its 23.0 backport.

[thaJeztah]

I think these two would already be ready to go for that;

• [0.11] vendor: github.com/containerd/containerd v1.6.21 buildkit#3884
• [0.11] Dockerfile: update runc v1.1.7, containerd v1.6.21 buildkit#3887

[crazy-max]

I think these two would already be ready to go for that;

* [[0.11] vendor: github.com/containerd/containerd v1.6.21 buildkit#3884](https://github.com/moby/buildkit/pull/3884)

* [[0.11] Dockerfile: update runc v1.1.7, containerd v1.6.21 buildkit#3887](https://github.com/moby/buildkit/pull/3887)

Ah right we would need these I guess. SGTM.

[crazy-max]

@thaJeztah

We don't need to pick to 23.0. BuildKit v0.10 is using Go 1.18.

[thaJeztah]

We don't need to pick to 23.0. BuildKit v0.10 is using Go 1.18.

Ah, right, I was thinking because the 23.0 branch is using go1.20 (or go1.19), but I guess we're "fine" if CI passes

[thaJeztah]

It's green!

LGTM

[crazy-max]

We don't need to pick to 23.0. BuildKit v0.10 is using Go 1.18.

Ah, right, I was thinking because the 23.0 branch is using go1.20 (or go1.19), but I guess we're "fine" if CI passes

Triggered the workflow manually on 23.0 branch to see how it goes: https://github.com/moby/moby/actions/runs/5535119683

[crazy-max]

We don't need to pick to 23.0. BuildKit v0.10 is using Go 1.18.

Ah, right, I was thinking because the 23.0 branch is using go1.20 (or go1.19), but I guess we're "fine" if CI passes

Triggered the workflow manually on 23.0 branch to see how it goes: https://github.com/moby/moby/actions/runs/5535119683

23.0 branch looks good: https://github.com/moby/moby/actions/runs/5535119683