Support transactionId prefix for clients

[Dejan Maric]

As a user of KTB, I would like to set up transactionalId ACLs for both producers and consumers that use prefixed ACLs. The way this is implemented today, it only allows for literal ACLs.

This is needed for spring-kafka clients. Spring-kafka defines a pool of producers with the same transactionIdPrefix and then each producer gets a transactionalId in the form of transactionalIdPrefix + n, where n starts with 0 and is incremented for each new producer (source: https://docs.spring.io/spring-kafka/reference/html/#transactions)

Describe the solution you'd like
I suggest adding another property called transactionIdPrefix and validate that only one of the [transactionId, transactionIdPrefix] id defined for the client. For the transactionIdPrefix julieOps would generate PREFIXED Write and Describe ACLs on TransactionalId resource.

[Dejan Maric]

Duplicate of #270