azurerm_container_registry: support for versionless encryption keys for ACR

[tjcorr]

Closes #11774

This allows for the use of versionless keys in ACR. I also included a small fix that allows for the upgrading of encryption keys.

[mbfrahry]

Hey @tj-corrigan! This fix looks great but I do want to ask for two tests here. One for checking that a versionless key works and another to confirm that we can update encryption

[tjcorr]

@mbfrahry I went ahead and added a test that creates an encrypted ACR with a specific version and then updates it to use the versionless key. Tests works fine on my machine but it is failing to properly cleanup since the keyvault is required to have purge_protection turned on:

Error: Error purging of Key "key-acr" (Key Vault "https://testkv210525173542901084.vault.azure.net/") : keyvault.BaseClient#PurgeDeletedKey: Failure responding to request: StatusCode=403 -- Original Error: autorest/azure: Service returned an error. Status=403 Code="Forbidden" Message="The user, group or application 'appid=642777f6-b38a-4f1d-88b4-4d7fe42927de;oid=a7bd45ed-2bf6-4d3f-9604-2930fa4f7c94;iss=https://sts.windows.net/72f988bf-86f1-41af-91ab-2d7cd011db47/' does not have keys purge permission on key vault 'testkv210525173542901084;location=eastus'. For help resolving this issue, please see https://go.microsoft.com/fwlink/?linkid=2125287" InnerError={"code":"ForbiddenByPolicy"}

It looks like the tests for DiskEncryptionSet have the same issue but I'm not sure how the CI/CD tools handle that situation.

[mbfrahry]

Not a problem! That'll work for us! Thanks for taking the time to get that test added

[mbfrahry]

LGTM!

[ghost]

This has been released in version 2.62.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example:

provider "azurerm" {
    version = "~> 2.62.0"
}
# ... other configuration ...

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.