fix: Abort instrumenting Lambda if runtime is unsupported

[lym953]

What does this PR do?

1. If Lambda runtime is unsupported, e.g. if it's an unresolved token, then abort instrumenting this Lambda function.
2. Change the required AWS CDK version from 2.134.0 to 2.146.0, so the unresolved token case can be tested.

Motivation

Right now, even if Node runtime is not supported, we still proceed with the rest of the steps of instrumentation. As a result, Lambda execution may fail because it can't find a Datadog wrapper that's supposed to be in the Lambda layer.

More in #314

Testing Guidelines

Steps

1. Make changes on the example TypeScript Lambda stack, so it uses an unresolved runtime 793365b
2. Deploy the stack

Result

1. A warning message is created:

2. Lambda function doesn't have the two layers installed
3. Lambda could run with no error

Additional Notes

Types of Changes

• Bug fix
• New feature
• Breaking change
• Misc (docs, refactoring, dependency upgrade, etc.)

Check all that apply

• This PR's description is comprehensive
• This PR contains breaking changes that are documented in the description
• This PR introduces new APIs or parameters that are documented and unlikely to change in the foreseeable future
• This PR impacts documentation, and it has been updated (or a ticket has been logged)
• This PR's changes are covered by the automated tests
• This PR collects user input/sensitive content into Datadog

[lym953]

/merge

[dd-devflow]

Devflow running: /merge

View all feedbacks in Devflow UI.

---

2024-12-06 22:38:14 UTC ℹ️ MergeQueue: pull request added to the queue

The median merge time in main is 9m.