Add dependency conflict check for httpx and httpx2 since there are two entry points

[Radhika Gupta (rads-1996)]

No description provided.

[Copilot]

🟡 Changes recommended

The new changelog entry is missing the consistent PR reference/link formatting used elsewhere in the file.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

This PR adds per-entry-point dependency conflict detection for the httpx and httpx2 OpenTelemetry instrumentations so that a dependency issue in one entry point does not prevent the other from being enabled.

Changes:

• Add an httpx/httpx2-specific dependency conflict check in _setup_instrumentations() before instrumenting each entry point.
• Add tests to validate that dependency conflicts skip only the affected entry point and that non-httpx instrumentations do not run the new check.
• Document the behavior change in the changelog.

File summaries

File	Description
src/microsoft/opentelemetry/_distro.py	Adds per-entry-point dependency conflict checks for httpx and httpx2 before instrumenting.
tests/test_instrumentation_options.py	Adds unit tests covering httpx/httpx2 conflict isolation and ensuring other instrumentations are unaffected.
CHANGELOG.md	Notes the new independent dependency check behavior for the two entry points.

Review details

• Files reviewed: 3/3 changed files
• Comments generated: 1
• Review effort level: Lite

---

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

[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,585.2	42,326.3	-1.75%	✅
azure_monitor_span	yes	292,397.7	295,858.0	-1.17%	✅
otel_log	no	48,517.8	48,398.0	+0.25%	✅
otel_span	no	89,790.8	90,612.5	-0.91%	✅