Azure: Rationalise image version tags

[northerngit]

Hi - The current use of AlmaLinux:8 images in Azure features timestamped versioning. While this provides detailed version information, it poses challenges in automated environments, particularly with Terraform configurations.

Timestamped versions, such as 8.8.2023072701 and 9.3.2023111602, require frequent manual updates in Terraform files with each new image release. This is time-consuming and susceptible to errors.

Current version examples:

almalinux:almalinux-x86_64:8-gen1:8.8.2023072701
almalinux:almalinux-x86_64:8-gen2:8.9.2023112501
almalinux:almalinux-x86_64:9-gen1:9.2.2023072701
almalinux:almalinux-x86_64:9-gen2:9.3.2023111602

It is suggested to introduce a major version tag (e.g., almalinux:almalinux-x86_64:8-gen2:8.9) that consistently points to the latest build of a major version. This approach would mitigate the need for updating minor version and build date details with each release, streamlining Terraform configuration management and enhancing efficiency in automated cloud deployments.

[esvmicrosoft]

Hello @northerngit ,

would version = "latest" satisfy the requirement? it works for the Azure provider.