Maintenance: Deploy new Lambda Layers in existing Layer account

[heitorlessa]

Technical debt

We've migrated from Lambda Layers internal pipeline to GitHub Actions and created new accounts.

Why is this needed?

Organizations that added our account in their org allow list will have trouble in adopting the new Layer.

Which area does this relate to?

Automation

Solution

No response

Acknowledgment

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

[github-actions]

This is now released under 1.26.6 version!