Configuration parameters. See RetryStatusOptions for details.
Handles client-controlled retry timing for transient failures. When a response
has a retryable status code (by default 408, 429, 500, 502, 503, 504),
the middleware waits according to the backoff strategy before retrying.
Unlike withRetryAfter, this middleware does not parse Retry-After headers.
Use this for general retry logic; use withRetryAfter when server timing matters.
Middleware that retries requests based on response status codes.