#1065 🐛 Fix using deprecated fargate resource quota

[deifyed]

Description

• Changes Fargate quota resource code in quota check from L-790AF391(number of pods) to L-3032A538(number of virtual
  CPU units)

Motivation and Context

Closes #1065

How to prove the effect of this PR?

Verify the bug

1. Verify that the AWS account you are using has 0 applied quota Fargate On-Demand resource count by going to
   AWS Console -> Service Quotas -> AWS Services -> AWS Fargate -> Fargate On-Demand resource count
2. Try to create a new cluster (It's the cluster reconciler that has the check) with the latest okctl
3. Verify that the process fails due to lack of available Fargate pods

Verify the fix

1. Try to create a new cluster with this PR on the same AWS account as above
2. Verify that the process does not fail due to lack of available Fargate Pods

Additional info

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.
• I have updated the release notes (for the next release).

[yngvark]

+1 for fast fix

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication