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 集群复现该故障。完成的标准是：命令能够处理报告的速率限制条件，而不会立即失败，并且所选择的行为已通过测试或复现得到验证。