Add Support for Kafka as Celery Broker in Flower

[Kexinist]

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Yes. Celery 5.6.0 introduced official support for Kafka as a broker, enabling users to leverage Kafka for task messaging. However, when configuring Flower (the Celery monitoring tool) with a Kafka broker URL (e.g., kafka://localhost:9092), Flower currently displays an error indicating that Kafka is not supported. This creates a gap in the monitoring ecosystem for Celery users who have adopted Kafka as their broker, as they cannot use Flower to monitor their workers and tasks effectively.
Describe the solution you'd like
A clear and concise description of what you want to happen.
I would like Flower to officially support Kafka as a broker, similar to how it supports Redis, RabbitMQ, and other brokers. Specifically, Flower should be able to parse and handle Kafka broker URLs, connect to Kafka clusters, and display real-time task and worker information—just as it does for other brokers. This would ensure a seamless monitoring experience for users who have upgraded to Celery 5.6.0+ and are using Kafka.

If there are any plans to implement this feature, I would appreciate an update on the timeline or any workarounds in the meantime. Thank you for your consideration!