Kafka topic names

[davecharron]

The current design uses a generated name for the trigger, global variable, data queue, and Kafka topic.
The name consists of the prefix 'AI' followed by 8 digits.
Ex. AI70363241

The name used for the IBM i objects may not be that important, as they are specific to the implementation and are managed by AIStream.
We do set a reasonably descriptive label on the objects to help identify them.
The Kafka topic name, on the other hand, should probably be something more descriptive.
This Kafdrop screenshot only lists 2 AIStream topics, and it's already difficult to determine which is which.

We could allow the user to specify the topic name, or we could build a descriptive name using the system, database, schema, and table name.

[mkwan01]

We are currently using the trigger id as the Kafka topic name. We also use the trigger id to create the DTAQ object under QSYS. Hence the trigger id must not be more than 10 characters. The solution is to decouple the topic name from the trigger id. The topic name is only created when we create the Kafka route. The topic name is in the format of "hostName_schemaName_tableName". The host name is fully qualified.

Example Kafka topic name:
p8adt05.rch.stglabs.ibm.com_QGPL_EMPTEST

[mkwan01]

I also found an issue when we print the DTAQ uri in verbose mode. We should hide the password field in the DTAQ uri.