docs: refresh SAM examples

[bpauwels]

Description of your changes

See #1140 for details

How to verify this change

Test the SAM examples

Related issues, RFCs

Issue Number: #1140

PR status

Is this ready for review?: YES
Is it a breaking change?: NO

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
• I have made corresponding changes to the examples
• My changes generate no new warnings
• The code coverage hasn't decreased
• I have added tests that prove my change is effective and works
• New and existing unit tests pass locally and in Github Actions
• Any dependent changes have been merged and published
• The PR title follows the conventional commit semantics

Breaking change checklist

• 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.

[dreamorosi]

I have left some comments, great work so far - I think we are getting very close!

[dreamorosi]

Tests is failing because the AWS SAM CLI that is present in the OS used by the CI is not the latest (1.60.0 - source). Node 18 support was introduced in version 1.65.0 (source).

We have two options here:

1. Use the setup-sam GitHub Action to explicitly set the version of the CLI, which would allow us to use the latest version.
2. Wait until the base image used in the CD updates the version.

Looking at the releases in the repo that maintains the images it seems that a new version that includes the latest SAM CLI is already available in pre-release. I'm not aware of their release schedule and from past releases I couldn't infer any.

I have opened a discussion to ask the question here, I would suggest to wait till Friday and reconvene. If by then we don't have the new version we'll set the explicit version and merge.

[github-actions]

@awslabs/aws-lambda-powertools-typescript No related issues found. Please ensure 'status/pending-release' label is applied before releasing.