refactor(psr3): align trace_id and span_id to snake_case

[drghdtjr]

Description

This PR aligns the traceId and spanId keys to trace_id and span_id (snake_case) in the PSR-3 instrumentation. This change ensures consistency with OpenTelemetry semantic conventions and aligns with other language SDKs as discussed in the issue.

Changes

• Modified Psr3Instrumentation.php to use snake_case for trace and span IDs.
• Updated Psr3InstrumentationTest.php to reflect these naming changes in integration tests.

Related Issue

Fixes #1744
open-telemetry/opentelemetry-php#1744

[welcome]

Thanks for opening your first pull request! If you haven't yet signed our Contributor License Agreement (CLA), then please do so that we can accept your contribution. A link should appear shortly in this PR if you have not already signed one.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: drghdtjr / name: drghdtjr (0db6b72, bac3c8b, da559ff)

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 83.44%. Comparing base (a3c02c8) to head (da559ff).

Additional details and impacted files

@@             Coverage Diff              @@
##               main     #498      +/-   ##
============================================
- Coverage     83.46%   83.44%   -0.02%     
  Complexity     2330     2330              
============================================
  Files           149      149              
  Lines          8791     8791              
============================================
- Hits           7337     7336       -1     
- Misses         1454     1455       +1     

Flag	Coverage Δ
Aws	93.37% <ø> (ø)
Context/Swoole	0.00% <ø> (ø)
Exporter/Instana	49.80% <ø> (ø)
Instrumentation/AwsSdk	82.00% <ø> (ø)
Instrumentation/CakePHP	20.42% <ø> (ø)
Instrumentation/CodeIgniter	79.31% <ø> (ø)
Instrumentation/Curl	86.88% <ø> (-0.28%)	⬇️
Instrumentation/Doctrine	92.82% <ø> (ø)
Instrumentation/ExtAmqp	88.80% <ø> (ø)
Instrumentation/ExtRdKafka	86.13% <ø> (ø)
Instrumentation/Guzzle	76.25% <ø> (ø)
Instrumentation/HttpAsyncClient	78.94% <ø> (ø)
Instrumentation/IO	0.00% <ø> (ø)
Instrumentation/Laravel	71.65% <ø> (ø)
Instrumentation/MongoDB	76.84% <ø> (ø)
Instrumentation/MySqli	93.39% <ø> (ø)
Instrumentation/OpenAIPHP	86.71% <ø> (ø)
Instrumentation/PDO	85.67% <ø> (ø)
Instrumentation/PostgreSql	91.36% <ø> (ø)
Instrumentation/Psr14	77.41% <ø> (ø)
Instrumentation/Psr15	89.74% <ø> (ø)
Instrumentation/Psr16	97.43% <ø> (ø)
Instrumentation/Psr18	79.41% <ø> (ø)
Instrumentation/Psr3	67.70% <100.00%> (ø)
Instrumentation/Psr6	97.56% <ø> (ø)
Instrumentation/ReactPHP	99.41% <ø> (ø)
Instrumentation/Session	94.28% <ø> (ø)
Instrumentation/Slim	84.21% <ø> (ø)
Instrumentation/Yii	83.33% <ø> (ø)
Logs/Monolog	100.00% <ø> (ø)
Propagation/CloudTrace	90.69% <ø> (ø)
Propagation/Instana	98.07% <ø> (ø)
Propagation/ServerTiming	94.73% <ø> (ø)
Propagation/TraceResponse	94.73% <ø> (ø)
ResourceDetectors/Azure	91.66% <ø> (ø)
ResourceDetectors/Container	93.02% <ø> (ø)
ResourceDetectors/DigitalOcean	100.00% <ø> (ø)
Sampler/Xray	78.38% <ø> (ø)
Shims/OpenTracing	92.99% <ø> (ø)
SqlCommenter	95.58% <ø> (ø)
Symfony	88.14% <ø> (ø)
Utils/Test	87.79% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
...c/Instrumentation/Psr3/src/Psr3Instrumentation.php	48.33% <100.00%> (ø)

... and 1 file with indirect coverage changes

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a3c02c8...da559ff. Read the comment docs.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[drghdtjr]

Hi @ChrisLightfootWild,
Could you please approve the workflows to run again?
Thank you!"

[drghdtjr]

"Hello @ChrisLightfootWild! I see that the checks are failing, but the errors are coming from the Symfony instrumentation and Sampler modules, which are outside the scope of my PSR-3 refactoring. Since these appear to be existing upstream issues, could you advise on how to proceed so we can merge this? Thanks!"

[brettmc]

@drghdtjr you can ignore those failures. If your PR didn't break it, you don't need to fix it.

[drghdtjr]

Thanks for the reviews @brettmc and @ChrisLightfootWild!

If there’s any feedback on the code, I’m happy to make updates. Otherwise, would it be okay to proceed with merging this PR?