[EKS] [request]: support parameter store in Fargate EKS

Current Behavior:
Currently Secret store CSI driver does not support Fargate. This is due to the fact that the Secret store CSI driver is deployed as a daemon set and EKS fargate do not support daemon sets.
refed: https://github.com/aws/secrets-store-csi-driver-provider-aws#requirements

And you will get this error:
_Warning FailedScheduling 101s fargate-scheduler Pod not supported on Fargate: volumes not supported: XXXX is of an unsupported volume Type_
The pod is always pending.

Expected Results:
As EC2 EKS, fargate EKS can also support parameter store feature.

Fix?
Just think out loud: can possible solution be side-car container as fluent-bit logging? or Fargate infra has a type I can allocate my resource which has this Secret store CSI driver running?

### Community Note

* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment

**Tell us about your request**
What do you want us to build?

**Which service(s) is this request for?**
This could be Fargate, ECS, EKS, ECR

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
What outcome are you trying to achieve, ultimately, and why is it hard/impossible to do right now? What is the impact of not having this problem solved? The more details you can provide, the better we'll be able to understand and solve the problem.

**Are you currently working around this issue?**
How are you currently solving this problem?

**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.)

Start with the Secret Store CSI Driver requirements linked in the issue and the reported Fargate scheduler error. Compare how parameter store support works on EC2-based EKS, then investigate whether Fargate offers a supported deployment model that can replace the daemon set. Done means parameter store is supported on Fargate EKS without the pod remaining pending.

Written by the indexing model from the issue text.