feat: Update resource naming conventions based on Azure standards

[Abdul-Microsoft]

Purpose

• This pull request introduces a consistent naming convention for Azure resources in the infra/main.bicep file and its associated modules. It achieves this by using abbreviations loaded from an external JSON file (abbreviations.json) and applying them throughout the codebase. Additionally, it includes changes to private endpoint configurations and network-related resources for improved clarity and alignment with the new naming convention.

Naming Convention Updates:

• Introduced a new abbrs variable to load abbreviations from abbreviations.json for consistent resource naming (infra/main.bicep).
• Updated resource names across various modules to use the abbreviations, including managed identities, log analytics workspaces, application insights, storage accounts, key vaults, and more (infra/main.bicep). [1] [2] [3] [4] [5] [6] [7] [8] [9] [10]

Private Endpoint Configuration:

• Simplified private endpoint names and custom network interface names in multiple modules, including AI services, Cosmos DB, Key Vault, and Storage Account modules. [1] [2] [3] [4] [5]

Network Resource Updates:

• Standardized naming for network security groups (e.g., web-nsg changed to nsg-web) and other network-related components like bastion hosts and jumpboxes (infra/modules/network.bicep). [1] [2] [3] [4] [5]
• Added a public IP address configuration for the bastion host module (infra/modules/network/bastionHost.bicep).

Virtual Machine Configuration:

• Updated the naming of OS disks and NIC configurations for virtual machines in the jumpbox module (infra/modules/network/jumpbox.bicep).
• Changed the availability zone for virtual machines from 2 to 0 for better flexibility (infra/modules/network/jumpbox.bicep).

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.4.3 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀