Description

Previously, the resilience pipeline used to create the Kusto databases had two shortcomings:

1. Only handled the throttle exception
2. Relatively long delay before retry

Address both of those issues by:

• Extract the resilience pipeline into its own internal class so it can be tested
• Update the pipeline to handle exceptions that implement Kusto's common interface
• Update the pipeline to use a shorter timeout but with more tries and an exponential backoff

Checklist

• Is this feature complete?
  • Yes. Ready to ship.
  • No. Follow-up changes expected.
• Are you including unit tests for the changes and scenario tests if relevant?
  • Yes
  • No
• Did you add public API?
  • Yes
    • If yes, did you have an API Review for it?
      • Yes
      • No
    • Did you add <remarks /> and <code /> elements on your triple slash comments?
      • Yes
      • No
  • No
• Does the change make any security assumptions or guarantees?
  • Yes
    • If yes, have you done a threat model and had a security review?
      • Yes
      • No
  • No
• Does the change require an update in our Aspire docs?
  • Yes
    • Link to aspire-docs issue (consider using one of the following templates):
      • New (or update) doc-idea template
      • New breaking-change template
      • New diagnostic template
  • No