breaking: Use sha256 to hash lambda traceId that are triggered by Step Functions and set _dd.p.tid

What does this PR do?

using the most significant 128 bits of sha256 (instead of current md5) to hash trace_id and the first 64 for span_id.
the 1st and 65th bit should be 0.
manually take:
- the first 64 bits from the sha256 hash for _dd.p.tid tag
- the 2nd 64 bits from the sha256 hash for traceId
- if it were for spanId, use sha256 hash for parentId (which is step function task's spanId)
ts-md5 package is remove.
@node/type in DevDependencies needs to be upgraded by running yarn add @types/node -D as suggested in this the issue https://github.com/microsoft/TypeScript/issues/51567
note that for the root span it has span_id in number but trace_id in hex

{
"trace": {
    "root_id": "3124668925291824462",
    "spans": {
        "3124668925291824462": {
            "trace_id": "41919d29ba4149cd40fcae25a0e4e323",
            "span_id": "3124668925291824462",
            "parent_id": "0",
            "start": 1716393574.422,
            "end": 1716393576.138,
            "duration": 1.716,
            "type": "stepfunctions",
            "service": "kimi-test-nodejs-linking",
            "name": "aws.stepfunctions",
            "resource": "kimi-test-nodejs-linking",
            "resource_hash": "c76d3199bc4b077",
            "host_id": 3884291,
            "hostname": "none",
            "env": "dev",
            "host_groups": [
                "env:dev"
            ],
...

Motivation

To support 128 bits trace IDs and to avoid showing up in security vulnerability scans, we are upgrading the hashing method (md5) to sha256.

Testing Guidelines

trace link
example traceId 41919d29ba4149cd40fcae25a0e4e323 is a hash, not a number anymore.
verified that the parent_id of the aws.lambda span matches the aws.stepfunctions.lambda task span.

Additional Notes

This is a breaking change that will affect all current Step Functions public beta users. And what will break is the Step Functions trace and Lambda traces linking.

Since this has to be done at some point, we want to put this change out before GA. Serverless-Integrations team will work with Sumedha and have some sort of announcement to let customers know the exact cut off time so that they can deploy their Lambda around the same time.

Referencing PR for implementing MD5

Types of Changes

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

Check all that apply

[x] This PR's description is comprehensive
[x] 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
[ ] This PR passes the integration tests (ask a Datadog member to run the tests)

DataDog / datadog-lambda-js