With provisioned concurrency, containers are pre-warmed before
invocations, causing module load timestamps to be captured minutes
(or hours) before the first invocation. This inflates aws.lambda.load
span durations to the full pre-warm gap rather than the actual load time.

Skip cold start span creation for provisioned-concurrency, consistent
with the existing fix for lambda-managed-instances (PR #717).
Fixes #723.

* chore: update tsconfig target to es2017

* chore: update tsconfig target to es2021

* Update error logs in throw-error-traced_node18.log

* Update throw-error-traced_node20.log

* Update throw-error-traced_node22.log

* Update throw-error-traced_node22.log

* Update throw-error-traced_node24.log

* Update async-metrics_node20.log

Updated log entries to reflect changes in function names and error handling.

* undo update async metric log update

---------

Co-authored-by: Olivier Nzia <[email protected]>

* set full url in http.url tag

* trigger CI

* Add span.kind=server to aws.lambda span

This aligns the tracer-created span with the extension's behavior,
enabling server-based features in Datadog APM for Lambda functions.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <[email protected]>

* Update integration test snapshots to include span.kind: server

Add span.kind: server tag to aws.lambda spans in snapshot files
for esm, process-input-traced, and status-code-500s tests across
all Node.js versions (18, 20, 22, 24).

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <[email protected]>

* Add span.kind=server to warm start spans in snapshots

* Fix duplicate span.kind entries in esm snapshots

---------

Co-authored-by: Claude Opus 4.5 <[email protected]>

Pin GitHub Actions

Co-authored-by: julien.doutre <[email protected]>