test(terraform): pin azurerm provider to 4.80.0

[Mani Bindra (maniSbindra)]

Summary

• pin the authorization-permission-mismatch E2E sample to hashicorp/azurerm 4.80.0
• prevent clean E2E runs from automatically selecting 4.81.0
• use the merge-group E2E run to validate whether the provider update is related to the persistent failures

Context

The last successful scheduled Terraform E2E run used azurerm 4.80.0. Persistent failures began when clean initialization started selecting 4.81.0. This pin is intentionally limited to the failing sample while the suspected provider behavior is investigated.

Relates to #311.

Validation

• terraform fmt -check samples/terraform/authorization-permission-mismatch/main.tf
• terraform init -backend=false -input=false selected azurerm 4.80.0

[Copilot]

Pull request overview

Pins the Terraform authorization-permission-mismatch E2E sample to a known-good hashicorp/azurerm version (4.80.0) to help confirm whether the recent provider auto-upgrade to 4.81.0 is the cause of the persistent E2E failures described in #311.

Changes:

• Adds a terraform.required_providers block for azurerm.
• Constrains azurerm to = 4.80.0 to prevent clean init from selecting 4.81.0 for this sample.

[Mani Bindra (maniSbindra)]

Superseded by #305. The azurerm 4.80.0 pin was moved there so the govulncheck and E2E fixes can be validated together in the merge queue.