Maintenance: optimize End to End tests mechanism to create powertools Layer once

[mploski]

Summary

Currently we create new powertools layer for every test group in our e2e tests. It means we create 3 layers per test execution. If we multiply it by number of Python runtime we run tests in parallel (python 3.7,3.8, 3.9) we have 9 layers built for every github action executed.
It consumes resources (CPU, IOPS, Network Bandwidth) and can slow down overall test execution on constraint environments like github action workers.

Why is this needed?

It optimize resource utilization on build machine and thus lower down time needed to conduct tests and enable better scalability/cost control

Which area does this relate to?

No response

Solution

No response

Acknowledgment

• This request meets Lambda Powertools Tenets
• Should this be considered in other Lambda Powertools languages? i.e. Java, TypeScript

[heitorlessa]

Implemented by #1466

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

This issue is now closed. Please be mindful that future comments are hard for our team to see.

If you need more assistance, please either tag a team member or open a new issue that references this one.

If you wish to keep having a conversation with other community members under this issue feel free to do so.

[github-actions]

This is now released under 1.28.0 version!