feat(layers): introduce new CDK Python constructor for Powertools Lambda Layer

[leandrodamascena]

Issue number: #5278

Summary

Changes

This PR introduces a new CDK Python constructor for creating Lambda Layers, replacing the previously used powertools-lambda-layer-cdk project. This change aims to simplify our project structure, improve control over dependencies, and enhance our release process efficiency.

We've decided to move away from the powertools-lambda-layer-cdk project due to some issues:

1. Projen usage: The powertools-lambda-layer-cdk uses projen, which has caused issues in the past, particularly with its obscure management of transitive dependencies.
2. Lack of documentation: The powertools-lambda-layer-cdk project is poorly documented, leading to uncertainties in our automation processes.
3. Unnecessary complexity: Using an external CDK constructor for a layer we have full control over adds unnecessary complexity to our project.
4. Release process slowdown: The external constructor has been slowing down our release process by approximately 10 minutes.

Changes

• Removed dependency on powertools-lambda-layer-cdk
• Introduced a new custom CDK Python constructor for creating Lambda Layers
• Adjusted CI/CD pipelines to utilize the new constructor
• Added a new quality check step for this constructor

User experience

Please share what the user experience looks like before and after this change

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.

[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 SonarCloud

[leandrodamascena]

working on the last changes before asking for review.

[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 SonarCloud

[leandrodamascena]

This constructor is running here: https://github.com/leandrodamascena/test-powertools-action/actions/runs/11231065553

[dreamorosi]

Thank you for working on this.

In the coming weeks I will write a small internal RFC to decide whether we should continue supporting the standalone CDK construct repository, and move this logic there or deprecate it.

As you pointed out, that repository is lacking a clear purpose and some of the decisions that were made created some tech debt that was not addressed promptly.

If we are to continue supporting that CDK construct we should solve these issues and define a clear support model.