feat(runtime): add Python 3.13 support

[leandrodamascena]

Issue number: #5411

Summary

Changes

Lambda already published the base image for Python 3.13 (preview mode) and then we can start adding support for this new runtime in Powertools.

User experience

WIP

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.

[dreamorosi]

CI is failing with

OSError: [Errno 28] No space left on device

😰

[leandrodamascena]

e2e test is green

https://github.com/aws-powertools/powertools-lambda-python/actions/runs/11828379716/job/32959447655

[leandrodamascena]

CI is failing with

OSError: [Errno 28] No space left on device

😰

To be honest, this was my fault. I was running the CDK layer tests with an matrix of all Python versions, but I don't need that because I don't want to test if it's being built on a specific Python version, we know that build, I want to know if given a Python Runtime I can build the dockefile and synthesize CloudFormation.

Lets wait the CI run again.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
3 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[dreamorosi]

Ok thanks- can we also address the SonarCloud findings?

[leandrodamascena]

3 New issues

I'd rather not change them. These warnings are related to the Dockerfile in the sense that you're deploying a Docker image and it can create extra layers, add unnecessary Docker layer space, and so on. But that's not our case, the only reason we use a Dockerfile is to build using the actual Lambda environment (base images) and address things like libraries that need to be installed for a specific architecture or OS, and architecture. We don't use this Dockerfile to serve Docker images to customers, we just "build" and extract the resulting files from that build.

I'll mark all of them as "accepted"

[dreamorosi]

Thanks for the hard work on this @leandrodamascena!

[leandrodamascena]

@dreamorosi ready for review.