Rework Kafka health check in manageiq-messaging-ready

[nasark]

• The push/pop approach for Kafka health checks is not ideal because this can lead to timing issues when dealing with multiple consumers (multiple appliances). Therefore using a simple call to retrieve metadata from the Kafka server, this will fail if the server is down which is ideal for a health check
• Kafka client connections should be closed to prevent issues with multiple consumers on the same topic

Depends on:

• [x] https://github.com/ManageIQ/manageiq-messaging/pull/88
• [x] https://github.com/ManageIQ/manageiq/pull/23020
• [x] https://github.com/ManageIQ/manageiq-messaging/pull/89

@miq-bot assign @agrare @miq-bot add_reviewers @agrare @miq-bot add_label bug

[miq-bot]

Checked commits https://github.com/nasark/manageiq-appliance/compare/ec0914c7802744c43fdd28259ea50f3451b027fe~...a4bf67fb40dd7d45c3d90f93167612604e833fc0 with ruby 2.7.8, rubocop 1.56.3, haml-lint 0.51.0, and yamllint 0 files checked, 0 offenses detected Everything looks fine. :cake:

[Fryguy]

Backported to radjabov in commit 37f57f195b1cfb087a7b816f823cf3a630e09b83.

commit 37f57f195b1cfb087a7b816f823cf3a630e09b83
Author: Adam Grare <adam@grare.com>
Date:   Fri May 3 16:17:04 2024 -0400

    Merge pull request #384 from nasark/close_kafka_broker_connection

    Rework Kafka health check in manageiq-messaging-ready

    (cherry picked from commit b3a5a1f99dd440ed776e53b4f4ae2e5b34442095)