Additional options for kafka clients

[mgotz]

I wanted to enable ssl encryption and authentication for the kafka communications in the alarm-system. This reqires several additional settings for the kafka consumer and producers.
This PR adds a kafka_properties preference to the phoebus client and a corresponding cmd option to the alarm-server, alarm-logger and alarm-config-logger. This preference is a path to a properties file to load additional kafka-client properties from. The properties file format and content is the same as the one for the kafka-console clients. This should provide a lot of flexibility to configure the kafka clients without adding a lot of extra preferences to phoebus.
In addition, I tried to add this to the existing cmd parse logic in the alarm-server. However, I found it very complicated to add an additional argument in the existing structure, while also ensuring that all combinations and also orders of arguments work properly. So, I rewrote the cmd argument parsing making the processing independent of the order the arguments were given. Hopefully, this makes it a bit more flexible and it removed some of the repetitive code.

[kasemir]

While there are many little changes, they're all just about adding a new kafka_properties(_file) parameter to the various methods. By default it's "" and basically ignored, so that should be fine.

Can you add some example for how to actually use ssl encryption and authentication?
For example, add a section to the https://github.com/ControlSystemStudio/phoebus/blob/master/app/alarm/Readme.md.
Towards the end, after "Demos" but before the final "Issues" paragraph, add a section

Encryption and Authentication
=======================

The default setup as described so far connects to Kafka without encryption nor authentication.
While this may be acceptable for a closed control system network, you can enable encryption and
require a user/password for kafka connections as follows.

Configure Kafka
----------------

In kafka/config/whatever.yml, add this to enable encrypted connections and ...

Configure CS-Studio UI, Alarm Server, Alarm Logger
----------------------------------------------------

Create a kafka properties file like this:

xxx =yyy
user=
password=

[shroffk]

Documentation would be great, @mgotz could you open a new PR with the documentation
I will merge this now since I want to commit changes to the alarm-logger in preparation for elastic 8 and want to avoid conflicts

[mgotz]

Wonderful, I will add some documentation and make a new PR

[shroffk]

@mgotz recently a discussion regarding the kafka group.id came up.

Is there a use case on your end where you would want o manage the group.id in a properties files instead of having a globally unique one being assigned at runtime for the service and clients?

I would like to remove the conditional check... and instead always set a uuid irrespective of what is set in the properties file.

        if (!kafka_props.containsKey("group.id")){

[kasemir]

#3647

[mgotz]

I don't have a use case to manage the group.id in the properties file.
My thinking was that if someone wants to manage the groupi.id in the properties file they could. However, it is not required. If you don't set it in the properties file it will get a unique ID, just like you don't need a kafka.properties file at all.