[Fargate] [request]: Fargate pods not to lie about Volumes at start up

**Tell us about your request**
When using Fargate nodes on EKS with EFS volumes the initial Event from the Pod is a lie
```
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning FailedScheduling 5m43s fargate-scheduler Pod not supported on Fargate: volumes not supported: persistence not supported because: persistentvolumeclaim "test-pvc" not found
```
Since August 2020 (https://aws.amazon.com/blogs/aws/new-aws-fargate-for-amazon-eks-now-supports-amazon-efs/) Fragate pods have supported EFS based Volumes

The PersistentVolumeClaim does exist in the correct namespace.

**Which service(s) is this request for?**
Fargate on EKS

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Given how long Fargate instances take to start this error is shown for a long time ( more than 10mins) and leads to confusion that this is the reason that the pod has not started yet and implies it will never start.

**Are you currently working around this issue?**
To remember that the error is a LIE

**Additional context**
Anything else we should know?

**Attachments**
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)

The issue names Fargate on EKS and provides an example FailedScheduling event, but it does not identify repository files, tests, or an implementation entry point. Start by confirming whether the reported event is still emitted for existing EFS-backed PVCs; done means the startup status no longer falsely reports the volume as unsupported.

Written by the indexing model from the issue text.