CI: run test:otel-thread-ctx explicitly in profiling.yml

The spec is technically already picked up by the top-level 'packages/dd-trace/test/*.spec.js'
glob in test:trace:core:ci (apm-capabilities.yml), but the file is
profiling-team-owned per CODEOWNERS. Adding a dedicated step in
profiling.yml gives the owning team direct failure visibility in their
own workflow.

Author: szegedi

.github/workflows/profiling.yml

@@ -32,6 +32,7 @@ jobs:
       - uses: ./.github/actions/install
       - run: npm run test:profiler:ci
       - run: npm run test:integration:profiler:coverage
+      - run: npm run test:otel-thread-ctx
       - uses: ./.github/actions/coverage
         with:
           flags: profiling-macos
@@ -60,6 +61,7 @@ jobs:
       - uses: ./.github/actions/node/latest
       - run: npm run test:profiler:ci
       - run: npm run test:integration:profiler:coverage
+      - run: npm run test:otel-thread-ctx
       - uses: ./.github/actions/coverage
         with:
           flags: profiling-ubuntu
@@ -118,6 +120,7 @@ jobs:
           ) | ForEach-Object { "$_=" | Out-File -FilePath $env:GITHUB_ENV -Append -Encoding utf8 }
       - run: npm run test:profiler:ci
       - run: npm run test:integration:profiler:coverage
+      - run: npm run test:otel-thread-ctx
       - uses: ./.github/actions/node-crash-report
         if: failure()
       # Upload any WER minidumps that landed during this job, even on