aws/ec2: properly paginate DescribeNetworkInterfaces results

[MitchLewis930]

PR_046

---

Note

Low Risk
Small change limited to AWS ENI listing request parameters; primary risk is altered API call sizing/throughput impacting rate limits or performance in large environments.

Overview
Ensures EC2 DescribeNetworkInterfaces requests consistently paginate by setting MaxResults on ENI listing calls, using a new default (defaults.ENIMaxResultsPerApiCall = 1000).

This updates the EC2 client’s ENI discovery paths (all-ENI, by-instance, and by-instances filters) to cap per-call results and rely on the paginator to fetch remaining pages.

^{Written by Cursor Bugbot for commit 7e21480. This will update automatically on new commits. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

[cursor]

MaxResults and NetworkInterfaceIds cannot be used together

High Severity

The AWS EC2 DescribeNetworkInterfaces API explicitly prohibits specifying both MaxResults and NetworkInterfaceIds in the same request. In describeNetworkInterfacesFromInstances, MaxResults is unconditionally set to 1000, and then NetworkInterfaceIds is conditionally set when enisListFromInstances is non-empty. When instances with ENIs exist, both parameters will be set, causing an AWS API error.