Bump Debian Bookworm Linux version to bookworm-20250224

[github-actions]

Bump Debian Bookworm version

Update the value of the base image (ARG DEBIAN_RELEASE) in the Dockerfile

changed lines [22] of file "/tmp/updatecli/github/jenkinsci/docker-agent/debian/Dockerfile"

Update the default value of the variable DEBIAN_RELEASE in the docker-bake.hcl

changes detected: path "variable.DEBIAN_RELEASE.default" updated from "bookworm-20250203" to "bookworm-20250224" in file "docker-bake.hcl"

GitHub Action workflow link

---

Created automatically by Updatecli Options: Most of Updatecli configuration is done via its manifest(s). If you close this pull request, Updatecli will automatically reopen it, the next time it runs. If you close this pull request and delete the base branch, Updatecli will automatically recreate it, erasing all previous commits made. Feel free to report any issues at github.com/updatecli/updatecli. If you find this tool useful, do not hesitate to star our GitHub repository as a sign of appreciation, and/or to tell us directly on our chat!

[dduportal]

The build is failing due to DockerHub rate limit errors:

ERROR: target agent_alpine_jdk17: failed to solve: alpine:3.21.3: failed to resolve source metadata for docker.io/library/alpine:3.21.3: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/library/alpine/manifests/sha256:a8560b36e8b8210634f77d9f7f9efd7ffa463e380b75e2e74aff4511df3ef88c: 429 Too Many Requests - Server message: toomanyrequests: You have reached your unauthenticated pull rate limit. https://www.docker.com/increase-rate-limit

But it is weird: the registry cache (hub-mirror) does not have any HTTP/429 error + the URL provided by Docker engine shows it is using DockerHub directly.

=> as if the buildx system is not honoring the registry mirror 🤔