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

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
OpenTelemetry.Instrumentation.AspNetCore (source)	nuget	minor	1.15.2 → 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 looks good — no concerns.

This PR bumps OpenTelemetry.Instrumentation.AspNetCore from 1.15.2 → 1.16.0, which is a minor/patch release of a well-maintained CNCF project. The change is consistent across all three locations:

• Directory.Packages.props (central version management)
• TUnit.Templates/content/TUnit.Aspire.Starter/…/ExampleNamespace.ServiceDefaults.csproj (template)
• examples/CloudShop/CloudShop.ServiceDefaults/CloudShop.ServiceDefaults.csproj (example project)

Observations:

• The version is aligned with the rest of the OpenTelemetry packages already at 1.16.0 (OpenTelemetry.Exporter.InMemory, OpenTelemetry.Exporter.OpenTelemetryProtocol, OpenTelemetry.Extensions.Hosting, OpenTelemetry.Instrumentation.Http). This brings the full suite to a consistent version, which is the right approach.
• The template project and example project have the version pinned inline rather than using the central Directory.Packages.props. This is a pre-existing pattern, not introduced here, but worth noting: if the template/example projects were moved to use Directory.Packages.props for OTel versions they'd only need one update per bump instead of three.

Safe to merge; auto-merge is already enabled.

[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.}