contrib/IBM/sarama.v1: stop using mockbroker for tests

[rarguelloF]

What does this PR do?

Change tests of IBM/sarama to use a real kafka broker instead of using sarama.NewMockBroker.

Motivation

The behavior of the mock broker has changed in future versions of IBM/sarama, which makes our v2 smoke tests fail. Instead of trying to hunt what changed and how to fix our tests with the new mock broker behavior, its better and more reliable to test things with an actual Kafka instance (which is how we test the rest of our Kafka integrations).

Reviewer's Checklist

• Changed code has unit tests for its functionality at or near 100% coverage.
• System-Tests covering this feature have been added and enabled with the va.b.c-dev version tag.
• There is a benchmark for any new code, or changes to existing code.
• If this interacts with the agent in a new way, a system test has been added.
• Add an appropriate team label so this PR gets put in the right place for the release notes.
• Non-trivial go.mod changes, e.g. adding new modules, are reviewed by @DataDog/dd-trace-go-guild.
• For internal contributors, a matching PR should be created to the v2-dev branch and reviewed by @DataDog/apm-go.

Unsure? Have a question? Request a review!

[darccio]

LGTM

[datadog-datadog-prod-us1]

Datadog Report

Branch report: rarguelloF/integration-tests-sarama
Commit report: 8676eeb
Test service: dd-trace-go

✅ 0 Failed, 3011 Passed, 25 Skipped, 2m 19.26s Total Time

[pr-commenter]

Benchmarks

Benchmark execution time: 2025-01-20 16:46:17

Comparing candidate commit f7d2f03 in PR branch rarguelloF/integration-tests-sarama with baseline commit 2e3193f in branch main.

Found 0 performance improvements and 0 performance regressions! Performance is the same for 58 metrics, 1 unstable metrics.