go1.22-runtime-tests failures

[milantracy]

Description

runtime tests failed, for example https://buildkite.com/gvisor/pipeline/builds/34118

##### Testing packages.
--
  | # go tool dist test -run=^container/ring$
  | ok  	container/ring	0.038s
  | 2025/01/04 12:05:09 Proctor checking in 2025-01-04 12:05:09.3513882 +0000 UTC m=+90.005853862
  | 2025/01/04 12:05:24 Proctor checking in 2025-01-04 12:05:24.351979646 +0000 UTC m=+105.006445286
  | --- FAIL: TestVerifyConnection (0.02s)
  | --- FAIL: TestVerifyConnection/TLSv12 (0.01s)
  | handshake_client_test.go:1784: RequireAndVerifyClientCert-FullHandshake: handshake failed: remote error: tls: bad certificate
  | --- FAIL: TestVerifyConnection/TLSv13 (0.01s)
  | handshake_client_test.go:1784: RequireAndVerifyClientCert-FullHandshake: handshake failed: remote error: tls: bad certificate
  | --- FAIL: TestResumptionKeepsOCSPAndSCT (0.01s)
  | --- FAIL: TestResumptionKeepsOCSPAndSCT/TLSv12 (0.00s)
  | handshake_client_test.go:2575: handshake failed: remote error: tls: bad certificate
  | --- FAIL: TestResumptionKeepsOCSPAndSCT/TLSv13 (0.00s)
  | handshake_client_test.go:2575: handshake failed: remote error: tls: bad certificate
  | --- FAIL: TestCrossVersionResume (0.01s)
  | --- FAIL: TestCrossVersionResume/TLSv12 (0.01s)
  | handshake_server_test.go:507: handshake did not resume at the same version
  | --- FAIL: TestCrossVersionResume/TLSv13 (0.01s)
  | handshake_server_test.go:507: handshake did not resume at the same version
  | FAIL
  | FAIL	crypto/tls	1.532s

Steps to reproduce

No response

runsc version

HEAD

docker version (if using docker)

uname

No response

kubectl (if using Kubernetes)

repo state (if built from source)

No response

runsc debug logs (if available)

runtime tests only

[milantracy]

i did some investigation to rule out gVisor regression.

Then I found golang/go#71077, which should be the fix

We shall wait for go1.22 and potentially go1.23 backports

I think we shall just refresh our image once they are ready