[metricbeat/module/kafka]: CI passes metricbeat integration tests with unreported errors

[khushijain21]

Kafka integration tests in metricbeat can pass with unreported errors when there is an issue with container handling. Such as when the test is attempting to use a "pre-existing" container. This could be misleading and even allow breaking changes to pass.

Build for ref: https://buildkite.com/elastic/beats-metricbeat/builds/11616#01936543-5c04-4bd5-bcff-08412dd6c8b6

Errors as seen in logs

ERROR: for metricbeat_9_0_0_4b253da3ea-snapshot_kafka_1  Cannot create container for service kafka: Conflict. The container name "/metricbeat_9_0_0_4b253da3ea-snapshot_kafka_1" is already in use by container "f06ce0d627f82450e05a94cbe116a8c8678a854b64e916a139ccd0ec974b07f6". You have to remove (or rename) that container to be able to reuse that name.

Some possible solutions:

• Do not pass the test in case of errors due to container creation
• Fix container handling issue similar to libbeat/tests/compose: Fix conflict in container creation for integration tests #36238

[elasticmachine]

Pinging @elastic/elastic-agent (Team:Elastic-Agent)