Localize DefaultProvisioningContextProvider interaction strings

[Copilot]

This PR addresses the localization of user-facing strings in DefaultProvisioningContextProvider that are displayed through the interaction service. Previously, all strings were hardcoded directly in the code, making them impossible to localize for international users.

Changes Made

Resource Infrastructure:

• Added Resources/AzureProvisioningStrings.resx with 12 localized strings covering all user-facing text in DefaultProvisioningContextProvider
• Generated corresponding AzureProvisioningStrings.Designer.cs file following the same pattern as other Aspire projects
• Build system automatically created .xlf files for 12 languages, enabling future translations

Code Updates:

• Updated DefaultProvisioningContextProvider to use AzureProvisioningStrings instead of hardcoded strings
• Added necessary using statement for Aspire.Hosting.Azure.Resources
• Maintained exact same text values to preserve backward compatibility

Localized Strings Include:

• Notification titles and messages for Azure provisioning prompts
• Input labels and placeholders for Location, Subscription ID, and Resource group fields
• Validation error messages for invalid subscription IDs and resource group names
• Documentation links and descriptions with markdown support

Testing:

• Added comprehensive unit tests in AzureProvisioningStringsTests.cs to verify all resource strings load correctly
• Existing integration tests continue to pass without modification, confirming backward compatibility
• Build system validates no regressions were introduced

Technical Approach

The implementation follows the established pattern used by other Aspire projects like Aspire.Hosting.Resources.InteractionStrings. Resource strings are accessed directly without dependency injection to match the existing codebase architecture, ensuring consistency across the project.

Example

Before:

var messageBarResult = await interactionService.PromptNotificationAsync(
    "Azure provisioning",
    "The model contains Azure resources that require an Azure Subscription.",
    // ...

After:

var messageBarResult = await interactionService.PromptNotificationAsync(
    AzureProvisioningStrings.NotificationTitle,
    AzureProvisioningStrings.NotificationMessage,
    // ...

This change enables future localization of the Azure provisioning experience while maintaining full backward compatibility with existing functionality.

Fixes #10960.

---

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

[Copilot]

Pull Request Overview

This PR localizes user-facing strings in the Azure provisioning experience by replacing hardcoded strings with resource strings from a new AzureProvisioningStrings.resx file. The change enables future internationalization of Azure provisioning prompts, input labels, and validation messages while maintaining backward compatibility.

• Adds comprehensive localization infrastructure with 12 resource strings covering all user-facing text
• Updates DefaultProvisioningContextProvider to use resource strings instead of hardcoded text
• Generates translation files for 12 languages with proper XLIFF structure

Reviewed Changes

Copilot reviewed 15 out of 16 changed files in this pull request and generated no comments.

File	Description
src/Aspire.Hosting.Azure/Resources/AzureProvisioningStrings.resx	Adds primary resource file with 12 localized strings for Azure provisioning UI
src/Aspire.Hosting.Azure/Resources/xlf/*.xlf	Generated XLIFF translation files for 12 languages with proper structure
src/Aspire.Hosting.Azure/Provisioning/Internal/DefaultProvisioningContextProvider.cs	Updates code to use resource strings instead of hardcoded text

Files not reviewed (1)

• src/Aspire.Hosting.Azure/Resources/AzureProvisioningStrings.Designer.cs: Language not supported

[captainsafia]

LGTM as far as the outputs in this for the CLI interaction.