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.

從 stackablectl stacklet list 命令使用的請求路徑開始，追蹤 Kubernetes API 錯誤的處理方式。檢查 kube-rs 是否已經為 HTTP 429 回應提供重試或節流行為，並在可能的情況下針對 EKS 叢集重現該失敗。完成的標準是：命令能夠處理回報的速率限制條件，而不會立即失敗，並且所選擇的行為已透過測試或重現得到驗證。