chore(deps): update dependency opentelemetry.instrumentation.http to 1.16.0

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
OpenTelemetry.Instrumentation.Http (source)	nuget	minor	1.15.1 → 1.16.0

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

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

---

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

---

This PR has been generated by Mend Renovate.

[claude]

Dependency Update Review: OpenTelemetry.Instrumentation.Http 1.15.1 → 1.16.0

This is a straightforward minor version bump generated by Renovate. The changes look correct and consistent.

What Changed

• OpenTelemetry.Instrumentation.Http bumped from 1.15.1 → 1.16.0 in three locations.

Observations

Version alignment across OTel packages: Most OpenTelemetry packages in this repo are now at 1.16.0, but OpenTelemetry.Instrumentation.AspNetCore is still pinned at 1.15.2. This isn't introduced by this PR (it pre-existed), but it's worth keeping an eye on — if 1.16.0 of AspNetCore instrumentation is available, a follow-up Renovate PR would be expected.

Template/example project duplication: The template (ExampleNamespace.ServiceDefaults.csproj) and example (CloudShop.ServiceDefaults.csproj) projects carry explicit Version attributes on their PackageReference items rather than deferring to Directory.Packages.props. This means version bumps require changes in multiple places (as seen here). If these projects are intended to be self-contained/distributable, this is acceptable by design — but if they're meant to stay in lockstep with the repo, they could be unified under central package management to reduce the maintenance surface. Not a blocker for this PR, just an architectural note.

Verdict

The update is mechanically correct and all three files are updated consistently. ✅ Safe to merge.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity

Metric	Results
Complexity	0

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}