Throttle requests when api-server tries to rate limit stackablectl

When trying to run stacklet list an an AWS eks cluster recently (replicated cluster, k8s 1.32) - the api-server was apparently unhappy about the rate at which requests were sent to retrieve details for Stackable objects.

soenke-desktop:~$ stackablectl stacklet list
An unrecoverable error occured: failed to execute stacklet (sub)command

Caused by these errors (recent errors listed first):
 1: failed to list stacklets
 2: failed to fetch data from the Kubernetes API
 3: failed to fetch data from Kubernetes API
 4: ApiError: storage is (re)initializing: TooManyRequests (ErrorResponse { status: "Failure", message: "storage is (re)initializing", reason: "TooManyRequests", code: 429 })
 5: storage is (re)initializing: TooManyRequests

We should probably somehow honour 429 status codes and throttle requests in that case. Or maybe implement this upstream in kube-rs.

Comienza por la ruta de solicitud utilizada por el comando stackablectl stacklet list y sigue cómo se gestionan los errores de la API de Kubernetes. Comprueba si kube-rs ya expone algún comportamiento de reintento o throttling para las respuestas HTTP 429, y reproduce el fallo contra un clúster de EKS si es posible. Se considera terminado cuando el comando gestiona la condición de límite de tasa indicada sin fallar inmediatamente, y el comportamiento elegido está verificado mediante pruebas o una reproducción.