feat(event_source): export SQSRecord in data_classes module

[AlisonVilela]

Issue number: #6637

Summary

Changes

Export SQSRecord class in the main aws_lambda_powertools.utilities.data_classes module to allow for more consistent import patterns when working with SQS events.

User experience

Before:
Developers need to use inconsistent import patterns:

from aws_lambda_powertools.utilities.data_classes import SQSEvent
from aws_lambda_powertools.utilities.data_classes.sqs_event import SQSRecord

After:
Developers can use a single, consistent import pattern:

from aws_lambda_powertools.utilities.data_classes import SQSEvent, SQSRecord

This improves developer experience by providing a more intuitive API when working with SQS events.

Checklist

If your change doesn't seem to apply, please leave them unchecked.

• Meet tenets criteria
• I have performed a self-review of this change
• Changes have been tested
• Changes are documented
• PR title follows conventional commit semantics

Is this a breaking change?

RFC issue number:

Checklist:

• Migration process documented
• Implement warnings (if it can live side by side)

Acknowledgment

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

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

[boring-cyborg]

Thanks a lot for your first contribution! Please check out our contributing guidelines and don't hesitate to ask whatever you need.
In the meantime, check out the #python channel on our Powertools for AWS Lambda Discord: Invite link

[AlisonVilela]

This doesn't fix a bug, as developers can already import SQSRecord directly from the submodule. The intent is simply to make the API more consistent and intuitive by allowing SQSEvent and SQSRecord to be imported from the same place, which aligns with how other event types are handled in the library.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.12%. Comparing base (d00c6a1) to head (113d726).
Report is 1 commits behind head on develop.

Additional details and impacted files

@@           Coverage Diff            @@
##           develop    #6639   +/-   ##
========================================
  Coverage    96.12%   96.12%           
========================================
  Files          253      253           
  Lines        12104    12104           
  Branches       902      902           
========================================
  Hits         11635    11635           
  Misses         369      369           
  Partials       100      100           

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[leandrodamascena]

Thanks for improving this experience @AlisonVilela! Approving!

[leandrodamascena]

Obrigado 🇧🇷

[boring-cyborg]

Awesome work, congrats on your first merged pull request and thank you for helping improve everyone's experience!