[EKS] [Feature]: Allow to use Fargate profiles in a different VPC

### 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**
Today when I configure a Fargate profile I can only choose private subnets within the same VPC where the cluster (Control Plane) lives. I would like to be able to select private subnets from a different VPC connected to my EKS cluster VPC.

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

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
If I need particular workloads to run inside a specific network to access private resources, I need to spin up a self-managed node group. Being able to spin up a Fargate profile in a different subnet would lower the operational burden quite a bit.

**Are you currently working around this issue?**
No

**Additional context**

**Attachments**

The issue describes EKS Fargate profiles using private subnets in a VPC different from the cluster VPC, but it names no repository files, tests, or implementation entry points. First clarify whether this roadmap request is actionable in this repository and define the required cross-VPC behavior before identifying completion criteria.

Written by the indexing model from the issue text.