add tag matching to Azure File storage class

Adding the tags should ensure that we do not match a storage account
that was created by someone else which would be undesirable.

Additionally it solves the problem of matching storage accounts with
private endpoints - currently driver can match those even if
`networkEndpointType` is unset. Using the tags and matching should make
this more predictable and driver should no longer match those.
However, even if this ever gets fixed, we should probably still keep
the tags to prevent matching "foreign" storage accounts.

Upstream issue: kubernetes-sigs/azurefile-csi-driver#2085

assets/overlays/azure-file/base/storageclass.yaml

@@ -6,7 +6,9 @@ metadata:
 provisioner: file.csi.azure.com
 allowVolumeExpansion: true
 parameters:
+  matchTags: "true"
   skuName: Standard_LRS  # available values: Standard_LRS, Standard_GRS, Standard_ZRS, Standard_RAGRS, Premium_LRS
+  tags: storageClassName=azurefile-csi
 reclaimPolicy: Delete
 volumeBindingMode: Immediate
 mountOptions:

assets/overlays/azure-file/generated/hypershift/storageclass.yaml

@@ -16,7 +16,9 @@ mountOptions:
 - nosharesock
 - actimeo=30
 parameters:
+  matchTags: "true"
   skuName: Standard_LRS
+  tags: storageClassName=azurefile-csi
 provisioner: file.csi.azure.com
 reclaimPolicy: Delete
 volumeBindingMode: Immediate

assets/overlays/azure-file/generated/standalone/storageclass.yaml

@@ -16,7 +16,9 @@ mountOptions:
 - nosharesock
 - actimeo=30
 parameters:
+  matchTags: "true"
   skuName: Standard_LRS
+  tags: storageClassName=azurefile-csi
 provisioner: file.csi.azure.com
 reclaimPolicy: Delete
 volumeBindingMode: Immediate