[chore][receiver/kafa] Update README on topic (#33678)

**Description:**
Errors are seen in the kafka receiver when different telemetry types are
being scraped from the same topic. A receiver instance will receive data
of an unexpected format (wrong telemetry type) and fail to parse. This
is expected and should be documented.

**Link to tracking Issue:** Resolves #31679

receiver/kafkareceiver/README.md

@@ -27,7 +27,8 @@ The following settings can be optionally configured:
 
 - `brokers` (default = localhost:9092): The list of kafka brokers
 - `resolve_canonical_bootstrap_servers_only` (default = false): Whether to resolve then reverse-lookup broker IPs during startup
-- `topic` (default = otlp_spans for traces, otlp_metrics for metrics, otlp_logs for logs): The name of the kafka topic to read from
+- `topic` (default = otlp_spans for traces, otlp_metrics for metrics, otlp_logs for logs): The name of the kafka topic to read from.
+ Only one telemetry type may be used for a given topic.
 - `encoding` (default = otlp_proto): The encoding of the payload received from kafka. Available encodings:
  - `otlp_proto`: the payload is deserialized to `ExportTraceServiceRequest`, `ExportLogsServiceRequest` or `ExportMetricsServiceRequest` respectively.
  - `jaeger_proto`: the payload is deserialized to a single Jaeger proto `Span`.