use DescribeNetworkInterfaces with deep filters

[sushrk]

Issue #, if available:
N/A
Description of changes:
Use DescribeNetworkInterfaces EC2 API call with deep filters in v1.5.0 release.
As pagination leads to more EC2 API calls, this can cause EC2 API throttling on the customer account. We will evaluate using pagination in the upcoming releases with some optimizations.

Add integration test case for validating EC2 permissions on the controller

• verify controller is unable to delete ENIs not provisioned by the controller or vpc-cni (missing eks:eni:owner and other required tags)
• verify controller is able to create network interface permission on ENIs tagged with eks:eni:owner=eks-vpc-resource-controller
• verify controller is unable to create network interface permission on ENIs not tagged with eks:eni:owner=eks-vpc-resource-controller

ginkgo -v --timeout 10m -- --cluster-kubeconfig=$KUBE_CONFIG_PATH --cluster-name=$CLUSTER_NAME --aws-region=$AWS_REGION --aws-vpc-id=$VPC_ID --cluster-role-arn XX

Ran 3 of 3 Specs in 126.137 seconds
SUCCESS! -- 3 Passed | 0 Failed | 0 Pending | 0 Skipped
PASS

Ginkgo ran 1 suite in 2m8.588011071s
Test Suite Passed

The test cases for validating other EC2 operations are successful is covered in perpodsg test suite.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[haouc]

lgtm