Add ConfigureInfrastructure sample for Kusto SKU customization to README

[Copilot]

Adds a comprehensive example to the Kusto integration README.md showing developers how to use the ConfigureInfrastructure method to customize the cluster SKU for development scenarios.

Problem

Developers using the Kusto integration may not always be able to use the emulator depending on the features they need. When they want to provision a real Kusto cluster for development, the default production SKU (Standard_D11_v2) can be expensive. They need guidance on how to use more cost-effective development SKUs like Dev(No SLA)_Standard_E2a_v4.

Solution

The new documentation example shows:

var kusto = builder.AddAzureKustoCluster("kusto")
                   .ConfigureInfrastructure(infrastructure =>
                   {
                       var cluster = infrastructure.GetProvisionableResources().OfType<KustoCluster>().Single();
                       cluster.Sku = new KustoSku()
                       {
                           Name = KustoSkuName.DevNoSlaStandardE2aV4,
                           Tier = KustoSkuTier.Basic,
                           Capacity = 1
                       };
                   });

Key Features

• Clear Use Case: Explains when developers would want to customize the SKU (emulator limitations vs. production costs)
• Complete Example: Provides a working code sample that follows established patterns
• Correct Configuration: Uses the proper SKU name (DevNoSlaStandardE2aV4), tier (Basic), and capacity (1) for the development SKU
• Minimal Changes: Only adds documentation without modifying any existing functionality

This enables developers to easily configure cost-effective Kusto clusters for development scenarios where the emulator doesn't meet their feature requirements.

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.