✨ feat: added kafka producer

[mhkarimi1383]

Tick the checkbox if you understand [x]:

• I have read and understand the pull request rules.

Description

Being able to monitor kafka instances by producing a message to them

I'm using producer since when kafka goes down or nodes became unavailable the producers are the first and most affected parts of ecosystem

NOTE: I have not tested SSL and some of the SASL Mechanisms, they should work but it would be great if someone test that thing :)

Type of change

Please delete any options that are not relevant.

• User interface (UI)
• New feature (non-breaking change which adds functionality)
• This change requires a documentation update

Checklist

• My code follows the style guidelines of this project
• I ran ESLint and other linters for modified files
• I have performed a self-review of my own code and tested it
• I have commented my code, particularly in hard-to-understand areas
  (including JSDoc for methods)
• My changes generate no new warnings
• My code needed automated testing. I have added them (this is optional task)

Screenshots (if any)

[CommanderStorm]

I only noticed that this is still a draft after reviewing this, sorry

In general, this monitor is well written, but also include screenshots of it working and how you tested this monitor. (are there things you did not test?)
Does this deal with #139 (comment) ? Is this a common problem with kafka or does this not need to be adressed? CC: @cruscio

[mhkarimi1383]

I only noticed that this is still a draft after reviewing this, sorry

In general, this monitor is well written, but also include screenshots of it working and how you tested this monitor. (are there things you did not test?)
Does this deal with #139 (comment) ? Is this a common problem with kafka or does this not need to be adressed? CC: @cruscio

Thanks for your review, but this one is not self-tested completely

But in Kafka (specially in K8s) when using Bootstrap Server instead of broker addresses your producers will get messed up when a node goes down, I don't know if this problem if coming from clients or no, but we want to make sure that producers are safe.

[CommanderStorm]

(I still would prefer to see HiddenInput instead of the regular input, but can accept that we only do this for the notificationproviders until now)

[louislam]

I added two brokers, one is working, another one is not working. The result is UP, wondering if it is correct.

[mhkarimi1383]

I added two brokers, one is working, another one is not working. The result is UP, wondering if it is correct.

Yes that's correct in kafka we are adding new multiple brokers to have high availability,
It will health check brokers

Also you can test that with one broker hostname that resolves to multiple brokers (In K8s Setup we have something called bootstrap server that acts like that) but when a node goes down our applications some times fail (Clients are bad or bootstrap server is returning bad addresses)

[mhkarimi1383]

But I don't know how KafkaJS handles load balancing and health checking, I found nothing in their docs

[chakflying]

The alignment of the mechanism dropdown is broken. I think vue-multiselect isn't needed here.

This also isn't setting the description (<p class="url"> in Details.vue) in the details page. Not a hard requirement but would be great if it's added.