fix(ec2): unique finding per Security Group in high risk ports check

[MarioRgzLpz]

Context

An issue was detected within ec2_securitygroup_allow_ingress_from_internet_to_high_risk_tcp_ports check because it loops over a list of ports and all the findings are generated with the same finding.uid which can’t be a possibility.

Description

Changed ec2_securitygroup_allow_ingress_from_internet_to_high_risk_tcp_ports logic to create one finding per security group instead of one finding per high risk port.

Checklist

• Are there new checks included in this PR? No
  • If so, do we need to update permissions for the provider? Please review this carefully.
• Review if the code is being covered by tests.
• Review if code is being documented following this specification https://github.com/google/styleguide/blob/gh-pages/pyguide.md#38-comments-and-docstrings
• Review if backport is needed.

License

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.94%. Comparing base (716558f) to head (0511dab).
Report is 764 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #5697   +/-   ##
=======================================
  Coverage   89.93%   89.94%           
=======================================
  Files        1124     1124           
  Lines       34812    34815    +3     
=======================================
+ Hits        31309    31315    +6     
+ Misses       3503     3500    -3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[MrCloudSec]

Great job!!

[prowler-bot]

💚 All backports created successfully

Status	Branch	Result
✅	v4.5

Questions ?

Please refer to the Backport tool documentation and see the Github Action logs for details