Improve default RetryHandler implementation

Is your feature request related to a problem? Please describe the problem.

SDK V5
As per incident: 2409111420000033
in case there is a low memory on server side the server returns 503 for other error codes.

In such cases SDK treats 404, 403 errors as if it is 503 and retries.

We were instructed by Microsoft support person of contact to implement RetryHandler on application side and retry only if "retry-after" header is present. However, it sounds like this should be handled in SDK side rather than us.

Describe the solution you'd like.

I would propose such cases, when Microsoft servers have low memory to be handled by SDK

Additional context?

No response

該 issue 沒有指定來源檔案或測試；先找出 Java SDK 中預設的 RetryHandler 實作及現有的 retry 測試。檢查 403、404、503 和 retry-after header 的處理方式，然後新增涵蓋範圍，顯示只有在要求的回應 header 允許 retry 時才會執行 retry。