feat(deps): update deps matching "@opentelemetry/*"

[trentm]

0.211.0 -> 0.212.0 @opentelemetry/api-logs (range-bump)
0.211.0 -> 0.212.0 @opentelemetry/instrumentation (range-bump)
0.211.0 -> 0.212.0 @opentelemetry/instrumentation-fetch (range-bump)
0.211.0 -> 0.212.0 @opentelemetry/instrumentation-grpc (range-bump)
0.211.0 -> 0.212.0 @opentelemetry/instrumentation-http (range-bump)
0.211.0 -> 0.212.0 @opentelemetry/instrumentation-xml-http-request (range-bump)
0.211.0 -> 0.212.0 @opentelemetry/sdk-logs (range-bump)
0.211.0 -> 0.212.0 @opentelemetry/sdk-node (range-bump)
2.5.0 -> 2.5.1 @opentelemetry/context-async-hooks
2.5.0 -> 2.5.1 @opentelemetry/context-zone-peer-dep
2.5.0 -> 2.5.1 @opentelemetry/core
2.5.0 -> 2.5.1 @opentelemetry/exporter-jaeger
2.5.0 -> 2.5.1 @opentelemetry/propagator-b3
2.5.0 -> 2.5.1 @opentelemetry/propagator-jaeger
2.5.0 -> 2.5.1 @opentelemetry/resources
2.5.0 -> 2.5.1 @opentelemetry/sdk-metrics
2.5.0 -> 2.5.1 @opentelemetry/sdk-trace-base
2.5.0 -> 2.5.1 @opentelemetry/sdk-trace-node
2.5.0 -> 2.5.1 @opentelemetry/sdk-trace-web

---

This is a follow-up to the core repo release earlier today (open-telemetry/opentelemetry-js#6402).

make release-please consider this PR "user-facing"

BEGIN_COMMIT_OVERRIDE
feat(deps): update deps matching "@opentelemetry/*" (#3383)
END_COMMIT_OVERRIDE

^^^ with chore in the commit title, release-please doesn't consider these changes user-facing (https://github.com/googleapis/release-please?tab=readme-ov-file#how-should-i-write-my-commits), and skips including the packages in a release.

[maryliag]

lgtm once tests are passing

[trentm]

So far, looking at a few failures, they all seem to be timing out the 2s test limit on some (all?) mocha tests. I'll try to re-run and see if that helps.

[pichlermarc]

So far, looking at a few failures, they all seem to be timing out the 2s test limit on some (all?) mocha tests. I'll try to re-run and see if that helps.

@trentm looks like they've been failing without the core updates too: #3346

[trentm]

Also looks like a flaky mongo db test here: https://github.com/open-telemetry/opentelemetry-js-contrib/actions/runs/21964225140/job/63450350204?pr=3383

[trentm]

So GH action runners are just too slammed or brokenly-slow to be useful right now:

    ExpressInstrumentation
      ✔ should work with ESM usage (3015ms)
      ✔ should work with Express routers (2297ms)
      ✔ should work with nested Express routers (3086ms)
      ✔ should set a correct transaction name for routes specified in RegEx (3488ms)
      ✔ should set a correct transaction name for routes consisting of array including numbers (2896ms)
      ✔ should set a correct transaction name for routes consisting of arrays of routes (3119ms)
      1) should set a correct transaction name for routes consisting of arrays of routes
      ✔ should handle more complex regexes in route arrays correctly (3131ms)
      ✔ should handle more complex regexes in route arrays correctly (2764ms)
      ✔ should handle more complex regexes in route arrays correctly (3230ms)
      ✔ should handle more complex regexes in route arrays correctly (3500ms)
      ✔ should handle more complex regexes in route arrays correctly (2591ms)
      2) should handle more complex regexes in route arrays correctly
      ✔ should handle more complex regexes in route arrays correctly (3115ms)
      ✔ should handle more complex regexes in route arrays correctly (2295ms)

Lovely.

[github-actions]

This package does not have an assigned component owner and is considered unmaintained. As such this package is in feature-freeze and this PR will be closed with 14 days unless a new owner or a sponsor (a member of @open-telemetry/javascript-approvers) for the feature is found. It is the responsibility of the author to find a sponsor for this feature.
Are you familiar with this package? Consider becoming a component owner.