lakectl - retry mechanism

[guy-har]

Description

Lakectl currently lacks client-side retry mechanisms for handling errors, such as throttling from the KV store. While lakeFS retries on the server side, these might still reach the retry limit. Implementing a client-side retry strategy could help mitigate issues often caused by autoscaling, and would allow clients to customize their retry settings. This proposal is targeted specifically at lakectl, following a user report. Additionally, returning 503 status codes from lakeFS may benefit other clients such our python SDK that uses urllib3 to automatically perform three retries on 503 errors.