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.

Inizia dal percorso della richiesta utilizzato dal comando stackablectl stacklet list e segui come vengono gestiti gli errori dell’API Kubernetes. Verifica se kube-rs espone già un comportamento di retry o throttling per le risposte HTTP 429 e, se possibile, riproduci il malfunzionamento su un cluster EKS. Il lavoro è completato quando il comando gestisce la condizione di rate limit segnalata senza fallire immediatamente e il comportamento scelto è verificato tramite test o riproduzione.