feat: implemented working query anonymizer

[tolgadur]

Jira: KCI-341

Description

This is the first userstory in the anonymize query epic KCI-340. Here, a class is defined that takes in a ksqldb query and returns the same statement with anonymised property names, column names, stream names etc.

For example, the following query...

ALTER STREAM my_stream ADD COLUMN c3 INT, ADD COLUMN c4 INT;

...is anonymised to:

ALTER STREAM stream1 (ADD COLUMN column1 INT, ADD COLUMN column2 INT);

The output in this story is all printed in the same line as discussed on Jira. The pretty printing according to specified rules from the product team is going to be done in KCI-377.

Testing done

Unit- and approval testing to make sure anonymizer works as expected.

Reviewer checklist

• Ensure docs are updated if necessary. (eg. if a user visible feature is being added or changed).
• Ensure relevant issues are linked (description should include text like "Fixes #")

[ghost]

@confluentinc It looks like @tolgadur just signed our Contributor License Agreement. 👍

Always at your service,

clabot

[swist]

Do you actually need this? If you know how to do it, we should depend on one version of approval tests throughout (via ksql-test-util or parent POM), if not let me know and I'll task myself up with that

[tolgadur]

You are right, I don't need it. I removed it now :)

[swist]

LGTM just two questions that would be good to have answers to before merging

[lct45]

Overall LGTM - had a few questions about handling UDFs / inline functions

[lct45]

Just to make sure I understand the anonymizing - there won't be a way to map what function is being described here to where the function is used, is that right?

[tolgadur]

Yes, that's right. I can add this if this is something we want though?

[lct45]

I think it's probably ok, depends on how much visibility product wants into functions