Use AzureKeyVaultName param for Azure Keyvault conformance test (#975)

Unlike the other conformance tests, the azure-keyvault.yaml config hardcodes the name of the
target resource which creates an issue for contributors wanting to set up their own test
environments. For example, different users sharing an Azure subscription may not be able
to manage the permissions on the target key vault individually, and will need to edit the
yaml to retarget against their own keyvault instance.

- Add `AzureKeyVaultName` environment variable as the value for `vaultName` in azure-keyvault.yaml
- Update conformance.yml github workflow to require AzureKeyVaultName secret.

.github/workflows/conformance.yml

@@ -87,7 +87,7 @@ jobs:
         - component: bindings.azure.storagequeues
           required-secrets: AzureBlobStorageAccessKey,AzureBlobStorageAccount,AzureBlobStorageQueue
         - component: secretstores.azure.keyvault
-          required-secrets: AzureKeyVaultSecretStoreTenantId,AzureKeyVaultSecretStoreClientId
+          required-secrets: AzureKeyVaultName,AzureKeyVaultSecretStoreTenantId,AzureKeyVaultSecretStoreClientId
           required-certs: AzureKeyVaultSecretStoreCert
         EOF
         )

tests/config/secretstores/azure/keyvault/azure-keyvault.yaml

@@ -6,7 +6,7 @@ spec:
   type: secretstores.azure.keyvault
   metadata:
   - name: vaultName
-    value: secretstore-keyvault
+    value: ${{AzureKeyVaultName}}
   - name: spnTenantId
     value: ${{AzureKeyVaultSecretStoreTenantId}}
   - name: spnClientId