Add normalized location to delete endpoint call

[joratz]

This pull request refactors how Azure region locations are normalized in the BotConfigurator service. The normalization logic, which converts display names like "Canada Central" into API-friendly names like "canadacentral", has been extracted into a dedicated helper method. This change improves maintainability and ensures consistent location formatting across endpoint creation and deletion operations.

Refactoring and Consistency Improvements:

• Extracted location normalization logic into a private NormalizeLocation helper method, replacing inline normalization in both CreateEndpointWithAgentBlueprintAs and DeleteEndpointWithAgentBlueprintAsync. This ensures consistent formatting and easier future updates. [1] [2]
• Updated the DeleteEndpointWithAgentBlueprintAsync method to use the normalized location value in both the request body and logging, aligning it with the creation workflow and preventing potential mismatches.

[Copilot]

Pull request overview

This pull request refactors the location normalization logic in the BotConfigurator service by extracting it into a dedicated helper method. The change improves code maintainability by eliminating duplicate normalization code and ensures consistent location formatting across both endpoint creation and deletion operations.

Key changes:

• Extracted inline location normalization logic into a reusable NormalizeLocation helper method
• Applied normalized location to the deletion endpoint request body and logging
• Fixed variable naming inconsistency in the delete method (renamed createEndpointBody to deleteEndpointBody)