chore(deps): Drop opentelemetry-instrumentation-httpx from the otel extra

docs/guides/trace_and_monitor_crawlers.mdx

@@ -35,6 +35,14 @@ In the following example, you can see the function `instrument_crawler` that con
     {InstrumentCrawler}
 </CodeBlock>
 
+The `otel` extra doesn't instrument HTTP clients. To also trace requests sent by <ApiLink to="class/HttpxHttpClient">`HttpxHttpClient`</ApiLink>, install the httpx instrumentation:
+
+```bash
+python -m pip install 'opentelemetry-instrumentation-httpx>=0.65b0'
+```
+
+Then call `HTTPX2ClientInstrumentor().instrument()` from `opentelemetry.instrumentation.httpx` next to the crawler instrumentation. `HttpxHttpClient` runs on the `httpx2` package, so `HTTPXClientInstrumentor` from the same module records no spans for it.
+
 ## Analyze the results
 
 In the Jaeger UI, you can search for different traces, apply filtering, compare traces, view their detailed attributes, view timing details, and more. For the detailed description of the tool's capabilities, please refer to the [Jaeger documentation](https://www.jaegertracing.io/docs/1.47/deployment/frontend-ui/#trace-page).

pyproject.toml

@@ -74,7 +74,6 @@ otel = [
     "opentelemetry-api>=1.34.1",
     "opentelemetry-distro[otlp]>=0.54",
     "opentelemetry-instrumentation>=0.54",
-    "opentelemetry-instrumentation-httpx>=0.54",
     "opentelemetry-sdk>=1.34.1",
     "opentelemetry-semantic-conventions>=0.54",
     "wrapt>=1.17.0",