[receiver/kafka] change topic configuration for consistency with default behavior

[wildum]

Description: The parameter topic is replaced by three parameters traces_topic, metrics_topic, and logs_topics. This change is consistent with the otlp receiver which provides traces_url_path, metrics_url_path, and logs_url_path parameters.

Previously it was not possible to use the same receiver config in different signal pipelines unless the topics were named according to the default values. With this change, the same config can be used in different pipelines because a topic can be specified for each signal.

Link to tracking Issue: #32735

Testing: Existing tests have been updated + local test with docker containers

Documentation: Updated to reflect the config changes

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 14 days.

[atoulme]

Interesting. Can we keep the topic field and deprecate it first?

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 14 days.

[wildum]

@atoulme I applied your suggestion:

• users that set the field "topic" will get a deprecation warning (but it still works as before)
• users who did not set the "topic" field explicitly (who are relying on the default values) will not have to do anything (seamless transition)
• trying to set both the field "topic" and the new "*_topic" fields results in a config error

LMK if that's ok for you

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 14 days.

[github-actions]

Closed as inactive. Feel free to reopen if this PR is still being worked on.