[Core] Introduce max delay duration limit in retry policy

[mssfang]

The retry-after could have a delay duration of 24hrs.
With introducing the max delay duration check before retry the request will solve the hanging there "forever" issue.

[vcolin7]

What's the reasoning behind setting an arbitrary limit on the Retry-After delay? What's the largest delay duration we realistically get in said header?

[azure-sdk]

API change check

API changes are not detected in this pull request.

[alzimmermsft]

If we do begin allowing this concept we should let this be configurable. But in the meanwhile, this can be worked around by configuring .setShouldRetryCondition when configuring the RetryOptions in a client. An example of this could be:

RetryOptions retryOptions = new RetryOptions(new ExponentialBackoffOptions()
    .setShouldRetryCondition( retryInfo -> {
        HttpResponse response = retryInfo.getResponse();
        if (response == null) {
            // return status based on the exception seen.
        }
        
        if (response.getStatusCode() != 429 && response.getStatusCode() != 503) {
            return false; // not a backoff scenarion, true error
        }

        Duration retryAfter = getRetryAfterDuration(response);
        return retryAfterBackoffIsAllowable(retryAfter); // logic to determine whether the backoff is too long.
    });