Static provisioning of PVC on EFS does not delete the data from mount path once we delete the pv and pvc.

Hello Team,
/kind bug
What happened?


I'm using Static Provisioning and I was wondering if it is expected behavior or a bug for my files to still be in the EFS file system even after we have cleaned up our pods and PVC/PVs. This is resulting in our meter usage keep going up even though we are redeploying new pods and the old files from already deleted pods and PVs are still in the file system.
I expected the Reclaim Policy: Delete option should be worked for static provisioning to delete the files on mount point+ mount path.
I tried replicated the issue but its working for dynamic provisioning but it is not working for static provisioning.

What you expected to happen?
After we delete the PVC/PV that was being used by the pods, it should have deleted the files in the attached Filesystem

How to reproduce it (as minimally and precisely as possible)?

1. The persistentVolumeReclaimPolicy: Delete should delete the mounth path in EFS and then need to delete the PVC.

```

apiVersion: v1
kind: PersistentVolume
metadata:
name: pv0003
spec:
capacity:
storage: 5Gi
volumeMode: Filesystem
accessModes:
- ReadWriteOnce
persistentVolumeReclaimPolicy: Delete

```

Environment
Kubernetes version (use kubectl version): 1.20*
Driver version: latest

As per the kubernetes document, https://kubernetes.io/docs/concepts/storage/persistent-volumes/, It is working with AWS awsElasticBlockStore - AWS Elastic Block Store (EBS) but didn't listed EFS

Start with the PersistentVolume YAML example and compare the documented Delete reclaim behavior for static and dynamic provisioning. Verify the behavior on Kubernetes 1.20 with the EFS driver; done means deleting the PVC/PV also removes the EFS mount path and its data, or clearly documents the supported behavior.

Written by the indexing model from the issue text.