Extending list of retryable codes

[SergeyMenshykh]

Motivation, Context and Description

This change is required to improve SK SDK resilience while working with REST API by extending list of HTTP status codes DefaultHttpRetryHandler retries on.

Contribution Checklist

• The code builds clean without any errors or warnings
• The PR follows SK Contribution Guidelines (https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
• The code follows the .NET coding conventions (https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions) verified with dotnet format
• All unit tests pass, and I have added new tests where possible
• I didn't break anyone 😄

[RogerBarreto]

Should we consider:

425(Too Early)?
507 InsufficientStorage?

[SergeyMenshykh]

Should we consider:

425(Too Early)? 507 InsufficientStorage?

Not sure about 425 one because it's related to a specific scenario when a client wants to send data in advance of the secure connection being set up to optimize the time required for TLS to create a secure connection.

There're no clear guidelines about the 507 one. Some sources say that it's a temporary issue implying that it can be retried the other ones say that it should not be retried in a scope of the same action?

Taking into account that it's always possible to add any additional status code when configuring Kernel, I would not add these codes now, and wait until they are requested be a default ones.

[adrianwyatt]

Should we consider:

425(Too Early)? 507 InsufficientStorage?

Good callout - we'll use this PR to align with MS practices, but I would welcome an issue for 425/507