chore(aws): migrate aws fixers to new class structure

[danibarranqueroo]

Context

With the new structure, all current AWS fixers have been refactored to follow the updated class-based pattern. The main changes are:

• Each fixer is now implemented as a class inheriting from AWSFixer.
• Information for each fixer are provided as class parameters (e.g., description, cost_impact, IAM policy, etc.).
• Associated tests have been updated to use the new class structure and verified to ensure all fixers continue to work as expected.
• For fixers that enable AWS services with direct cost implications (e.g., GuardDuty, SecurityHub, Access Analyzer), the cost_impact and cost_description fields have been set accordingly.

Description

Modified all the AWS fixers and the unit tests.

Checklist

• Are there new checks included in this PR? Yes / 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.
• [ ] Review if is needed to change the Readme.md
• [ ] Ensure new entries are added to CHANGELOG.md, if applicable.

API

• [ ] Verify if API specs need to be regenerated.
• [ ] Check if version updates are required (e.g., specs, Poetry, etc.).
• [ ] Ensure new entries are added to CHANGELOG.md, if applicable.

License

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