Bump azure-core-version to match the exporter changes

[Radhika Gupta (rads-1996)]

Will merge once the exporter version with the same bump is released to avoid conflicts.

[github-actions]

Performance comparison

Threshold: regressions >15.0% on gating scenarios fail the build. Higher ops/s is better; positive Δ means the PR is slower.

Scenario	Gating	Baseline (ops/s)	Candidate (ops/s)	Δ %	Status
azure_monitor_log	yes	41,380.5	41,498.9	-0.29%	✅
azure_monitor_span	yes	311,090.4	309,119.0	+0.64%	✅
otel_log	no	49,625.3	49,825.6	-0.40%	✅
otel_span	no	90,522.3	89,710.2	+0.91%	✅

[Copilot]

Copilot review overview

🟡 Changes recommended

Regenerate uv.lock to keep dependency metadata consistent.

Get a fresh assessment by requesting another Copilot review.

Review effort: Lite
Findings: 1

Open (1)

• Regenerate uv.lock to update azure-core dependency metadata · New

What changed in this PR

Raises the minimum azure-core version to align with exporter changes.

Changes:

• Updates the lower bound from 1.28.0 to 1.38.0.
• Requires regenerating uv.lock to reflect the updated constraint.

File	Summary
pyproject.toml	Updates the azure-core dependency constraint. A moderate issue remains: regenerate uv.lock.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.