Change HttpLogOptions to be HttpInstrumentationOptions, update docs

[lmolkova]

In this episode, we

• Change HttpLogOptions to configure all HTTP instrumentation. It extends InstrumentationOptions and is called HttpInstrumentationOptions. It's now part of HttpTrait
• Revisit Http log level detail - it's now exposed as a couple of boolean flags:
  • BASIC is now on by-default via distributed traces, no need to additionally log the same info
  • HEADERs is now the default mode when HTTP logging is enabled
  • BODY (no headers) is not possible anymore
    This matches current and proposed .NET behavior
• Minor cleanup

Thoughts/doubts on the API changes:

1. HttpInstrumentationOptions is flat. Some of it applies to logging only (headers).

   I don't envision tons of tracing and metrics options there or in InstrumentationOptions - configuration would be done on the otel side, our fallback does not need to be customizable, so having dedicated TracingOptions or MetricsOptions seems to be an overkill.

   Separating HttpLogOptions (so it's clear they only affect logs) is an alternative, but it'd be a mouthful to write
   new HttpInstrumentationOptions<>().setHttpLogOptions(new HttpLogOptions().setLoggingEnabled(true)) vs
   new HttpInstrumentationOptions<>().setLoggingEnabled(true))

2. There are examples when SDKs need to provide more tracing/metrics/logging options (Cosmos has quite a few, SB/EH would need some) - they would need to extend either InstrumentationOptions or HttpInstrumentationOptions depending on the protocol.

[azure-sdk]

API change check

APIView has identified API level changes in this PR and created following API reviews.

io.clientcore:core