.Net: Removing internal HttpRetry Abstraction and Implementation

[RogerBarreto]

Motivation and Context

⚠️ This is a breaking change.

Reduce the responsibility surface of Semantic Kernel regarding Resiliency implementations, keeping only the abstractions that can be delegated and handling by well know resiliency libraries and custom implementations.

Resolves #2271
Closes #2271

Description

This change removes and deprecates the usage of Retry implementations in our Resiliency namespace with NullHttpHandlerFactory implementations.

Changed our examples using Polly Handlers to handle most common retrial scenarios.

Contribution Checklist

• The code builds clean without any errors or warnings
• The PR follows the SK Contribution Guidelines and the pre-submission formatting script raises no violations
• All unit tests pass, and I have added new tests where possible
• I didn't break anyone 😄

[shawncal]

Pausing this PR due to its impact, until after next nuget release. Please continue to review and apply changes -- just don't merge!

[shawncal]

@SergeyMenshykh any thoughts or concerns here? Possible conflicts with error handling plans?

[SergeyMenshykh]

@SergeyMenshykh any thoughts or concerns here? Possible conflicts with error handling plans?

I welcome the idea of minimizing SK SDK API surface and removing all infra code that is not related to SK SDK domain. I don't see and conflicts with error handling.

[lemillermicrosoft]

So now there will be no retry handling by default? That seems like a big change that will have negative impact in developer and user experience.

[lemillermicrosoft]

Sorry for the random comments.

[lemillermicrosoft]

Very concerned about this removal without a replacement that doesn't require the user to copy code from our KernelSyntaxExamples project. This feels like it should be a core concept of SK and helping users leverage LLMs.

At minimum, there should be an ADR to make sure the various SDK flavors are aligned on expectations going forward.

Approving though to remove my blocking review.

https://platform.openai.com/docs/guides/rate-limits/retrying-with-exponential-backoff

https://api.python.langchain.com/en/latest/_modules/langchain/llms/openai.html#completion_with_retry

[RogerBarreto]

Closing this in favor of PR #2656