fix(deps): update otel core experimental to ^0.46.0 - autoclosed

[renovate-bot]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@opentelemetry/exporter-metrics-otlp-grpc (source)	^0.45.1 -> ^0.46.0
@opentelemetry/instrumentation (source)	^0.45.1 -> ^0.46.0
@opentelemetry/instrumentation-fetch (source)	^0.45.1 -> ^0.46.0
@opentelemetry/instrumentation-grpc (source)	^0.45.1 -> ^0.46.0
@opentelemetry/instrumentation-http (source)	^0.45.1 -> ^0.46.0
@opentelemetry/instrumentation-xml-http-request (source)	^0.45.1 -> ^0.46.0
@opentelemetry/sdk-node (source)	^0.45.1 -> ^0.46.0

---

Release Notes

open-telemetry/opentelemetry-js (@​opentelemetry/exporter-metrics-otlp-grpc)

v0.46.0

Compare Source

---

Configuration

📅 Schedule: Branch creation - "before 3am every weekday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[trentm]

I notice that the @opentelemetry/instrumentation package was not updated for "packages/opentelemetry-sampler-aws-xray". I think that is because it has an outdated dependency on "@opentelemetry/contrib-test-utils": "^0.34.0".

opentelemetry-js-contrib/packages/opentelemetry-sampler-aws-xray/package.json

Line 54 in 7d110d5

"@opentelemetry/contrib-test-utils": "^0.34.0",

That should be "^0.35.0".

Why is that out of date? It looks like that was not updated in #1798 when all other deps on @opentelemetry/contrib-test-utils were updated.

So perhaps we should update that dep first (or as part of this change) and then re-generate the update here?

[trentm]

I can push a fix to this branch that does that, but we still get the npm run compile errors shown in the "unit-test" CI job failures. I'm not sure what the issue is with those.