r/key_vault_(key|secret): updating the latest version when updating metadata

[tombuildsstuff]

This PR updates the Key Vault Key & Key Vault Secret resources to update the latest version of the Key/Secret, rather than for an older version

Since this resource doesn't have a concept of managing multiple versions - and we currently update the latest version for other fields, this behaviourally makes sense; but arguably there's a case for a singular version of these resources (e.g. "this version of this key vault secret") - but I'm not sure how useful that would be in a TF context.

$ TF_ACC=1 go test -v ./azurerm/internal/services/keyvault/tests/ -run=TestAccAzureRMKeyVaultKey_updatedExternally
=== RUN   TestAccAzureRMKeyVaultKey_updatedExternally
=== PAUSE TestAccAzureRMKeyVaultKey_updatedExternally
=== CONT  TestAccAzureRMKeyVaultKey_updatedExternally
--- PASS: TestAccAzureRMKeyVaultKey_updatedExternally (284.49s)
PASS
ok  	github.com/terraform-providers/terraform-provider-azurerm/azurerm/internal/services/keyvault/tests	284.541s

Fixes #6222
Supersedes #7841

[jackofallops]

LGTM 👍

[tombuildsstuff]

Tests pass:

[ghost]

This has been released in version 2.26.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.26.0"
}
# ... other configuration ...

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!