feat(layers): add arm64 to integration test matrix

[dreamorosi]

Description of your changes

This PR adds the AWS Lambda arm64 architecture to the test matrix for our integration tests.

With this addition the tests are now run on both architectures and for all the supported runtimes.

Since we don't use any architecture-specific package, nor any binary or native module, at least for the time being we can afford bundling the utilities once and using the same bundle on both x86_64 and arm64.

The goal of these tests is to continuously verify that the utilities are compatible on both architectures on Lambda.

The PR also shortens the prefixes of all tests by removing the E2E string from the name, changing them from Logger-E2E to just Logger. This is done to account for the addition of the architecture in the name. The full name for the Stack and resources deployed as part of the test will be Logger-18-arm-12345-featureName.

Important

While the PR will be merged on main shortly, we want to take a few weeks of time to run tests and thoroughly ensure that we don't need to build the utilities on arm. For this reason we plan on marking the layers as arm64-ready only as part of our upcoming v2 release (#1714).

Related issues, RFCs

Issue number: #1374

Checklist

• My changes meet the tenets criteria
• I have performed a self-review of my own code
• I have commented my code where necessary, particularly in areas that should be flagged with a TODO, or hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my change is effective and works
• The PR title follows the conventional commit semantics

Breaking change checklist

Is it a breaking change?: NO

• I have documented the migration process
• I have added, implemented necessary warnings (if it can live side by side)

---

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]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[dreamorosi]

Successful integration test with both architectures: https://github.com/aws-powertools/powertools-lambda-typescript/actions/runs/6331812964