fix(ingestor): retry with backoff management commands on 429 and >=500 errors

[matucker-msft]

No description provided.

[Copilot]

Pull Request Overview

This PR implements automatic retry logic with exponential backoff for Kusto management commands in the ADX ingestor. The primary purpose is to improve reliability when interacting with Azure Data Explorer by handling transient failures gracefully.

• Adds a new retry mechanism that handles HTTP 429 (throttling), 5xx server errors, and other transient Kusto SDK errors
• Wraps all existing Kusto management operations with retry logic using exponential backoff
• Uses Kubernetes wait utilities for consistent backoff behavior with configurable parameters

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.

File	Description
ingestor/adx/retry.go	New file implementing retry logic with exponential backoff for Kusto management commands
ingestor/adx/uploader.go	Wraps cluster details query with retry mechanism
ingestor/adx/syncer.go	Wraps all management operations (table creation, mapping, functions, policies) with retry logic