Maintenance: simplify script to update layer ARN

[dreamorosi]

Summary

The current script at .github/scripts/update_layer_arn.sh was built to handle different ARNs and different version numbers across regions.

It served us well, but now that we have settled on always keeping version numbers aligned, we don't need all the complexity included in it, and instead we can just take a new Lambda layer version as input and update the documentation accordingly.

We should update the workflow to do exactly this.

Why is this needed?

So that we can keep things simple and remove unneeded code.

Which area does this relate to?

Automation

Solution

No response

Acknowledgment

• This request meets Powertools for AWS Lambda (TypeScript) Tenets
• Should this be considered in other Powertools for AWS Lambda languages? i.e. Python, Java, and .NET

Future readers

Please react with 👍 and your use case to help us understand customer demand.