[EKS][Fargate] [request]: ResourceQuotaScopeSelectors for Fargate

### 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?

`ResourceQuotaScopeSelectors` for Fargate

**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?**

Comming with version 1.17, we can add the Resource quota for `PriorityClass` for the pods scheduled on normal worker nodes. However, with fargate, the `priorityClassName` is overwritten by `system-node-critical`. Therefore, I suggest adding this feature to fargate, so that we can have a better resource quota management for the fargate pods.

Start by reviewing the request for ResourceQuotaScopeSelectors on Fargate and the described priorityClassName behavior for EKS pods. The issue names no repository files, tests, implementation entry point, or acceptance criteria, so confirm the expected behavior and scope with maintainers before identifying what completion would require.

Written by the indexing model from the issue text.