enhancement(kafka sink): Add support for traces in kafka sink

[Azyrys]

Summary

Add support for traces for kafka sink.

Vector configuration

Wrote and ran integration tests.

How did you test this PR?

Added integration test, traces are supported in the kafka source so sink shouldn't be problematic in any way

Change Type

• Bug fix
• New feature
• Non-functional (chore, refactoring, docs)
• Performance

Is this a breaking change?

• Yes
• No

Does this PR include user facing changes?

• Yes. Please add a changelog fragment based on our guidelines.
• No. A maintainer will apply the no-changelog label to this PR.

References

• Closes: Kafka sink should support Trace output #18252

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[Azyrys]

I have read the CLA Document and I hereby sign the CLA

[elohmeier]

Thanks for the fix. I've tested this code locally by sending OTel data through a Vector ingress into Kafka and out using a Vector egress into Grafana Tempo and can confirm it works.

[zbirenbaum]

Awesome fix any chance we could get a review on this? Have to build from source until then for my use case...

[Azyrys]

@pront @rtrieu @thomasqueirozb Can someone from the maintainers team have a look?

[pront]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Breezy!

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[pront]

Thanks!