refactor: standardize naming conventions and parameter handling in Bicep templates1

[Harmanpreet-Microsoft]

Purpose

This pull request focuses on standardizing naming conventions and improving parameter handling in the Bicep infrastructure files. The most significant changes involve replacing inconsistent variable names, refining resource prefixes, and ensuring that parameters conform to updated naming and length constraints.

Naming Convention Updates:

• Updated variable names to replace prefixCleaned with ResourcePrefix across multiple resources, ensuring consistency in naming conventions. (infra/main.bicep: [1] [2] [3] [4] [5] [6] [7]
• Renamed variables like aiServicesName to azureAiServicesName for clarity and alignment with Azure naming standards. (infra/main.bicep: infra/main.bicepL81-R77)

Parameter Refinements:

• Changed the ResourcePrefix parameter to Prefix with updated constraints (3-20 characters) and added logic to truncate longer values to 20 characters. (infra/main.bicep: infra/main.bicepL2-R5)
• Updated parameter descriptions to better reflect usage and constraints. (infra/main.bicep: infra/main.bicepL2-R5)

Resource Name Adjustments:

• Standardized resource names by appending ResourcePrefix to ensure unique and descriptive names for resources like storage containers, AI services, and container apps. (infra/main.bicep: [1] [2] [3] [4]

Variable Simplifications:

• Simplified the construction of resource names by directly using ResourcePrefix and removing unnecessary transformations like replace operations. (infra/main.bicep: infra/main.bicepL52-R52)
• Removed redundant variables like aiHubName and replaced them with updated counterparts (azureAiHubName). (infra/deploy_ai_foundry.bicep: infra/deploy_ai_foundry.bicepL14-L30)
• ...

Does this introduce a breaking change?

• Yes
• No

Golden Path Validation

• I have tested the primary workflows (the "golden path") to ensure they function correctly without errors.

Deployment Validation

• I have validated the deployment process successfully and all services are running as expected with this change.

What to Check

Verify that the following are valid

• ...

Other Information

[github-actions]

🎉 This PR is included in version 1.3.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀