[Bug] Issue with glibc version GLIBC_2.34 and GLIBC_2.32 not found in earlier operator tags

[kevin85421]

Why are these changes needed?

#2205 changes the base image of Dockerfile.buildx from registry.access.redhat.com/ubi9/ubi-minimal:9.3 to gcr.io/distroless/base-debian11:nonroot which uses GLIBC_2.31. However, KubeRay operator requires GLIBC_2.32 and GLIBC_2.34. KubeRay operator Pod will fail with the following logs:

/manager: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /manager)
/manager: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /manager)

This issue is similar to GoogleContainerTools/distroless#1342, so this PR upgrades the base image from debian11 to debian12.

I can reproduce the issue by pulling images that are built by GitHub Actions. However, when I build the image following the same steps as GitHub Actions and then publish it to Quay, the issue does not occur.

CGO_ENABLED=1 GOOS=linux GOARCH=amd64 go build -tags strictfipsruntime -a -o manager-amd64 main.go
CC=aarch64-linux-gnu-gcc CGO_ENABLED=1 GOOS=linux GOARCH=arm64 go build -tags strictfipsruntime -a -o manager-arm64 main.go
docker buildx build --push --platform linux/amd64,linux/arm64 --attest type=provenance,disabled=true -t quay.io/kevin85421/kuberay:test --file Dockerfile.buildx .

In order to reproduce the issue, I used https://github.com/ray-project/kuberay/blob/master/.github/workflows/image-release.yaml to build multi-arch images and publish to my Quay account.

Related issue number

Closes #2270

Checks

• I've made sure the tests are passing.
• Testing Strategy
  • Unit tests
  • Manual tests
  • This PR is not tested :(