Add glibc version constraints to the kubelet package

https://github.com/kubernetes/kubernetes/pull/118996 (https://github.com/kubernetes/release/issues/3076) will land in Kubernetes 1.29, containing a switch to debian:bookworm. This means we now require glibc 2.36 (compared to 2.31 on bullseye) for non static binaries like the kubelet.

The package of the kubelet could contain a constraint like this to highlight possible incompatibilities:

```
Requires: glibc >= 2.36
```

This needs to be done per release branch, while only affecting 1.29. We could also add a similar constraint to previous release branches (with 2.31).

cc @kubernetes/release-managers

Start by locating the kubelet package metadata and release-branch packaging configuration in this repository. Compare the glibc requirement for Kubernetes 1.29 with the 2.31 requirement for earlier branches, then verify that the appropriate constraint is present on each affected branch.

Written by the indexing model from the issue text.