Support connector hints

[jogrogan]

Two changes:

• Adds hints to source objects to show up in the connector. It's a very real use case where a user may want to pass through hint information maybe as to the consumer group or something else configurable in flink.
• Passes through a "pipelineName" that will show up in the source/sink. This will be necessary for template parameters that require pipeline-uniqueness.

[ryannedolan]

re viewName, K8sMaterializedViewDeployer sets {{name}} for pipeline uniqueness purposes. Do we need more than that?

[jogrogan]

re viewName, K8sMaterializedViewDeployer sets {{name}} for pipeline uniqueness purposes. Do we need more than that?

Name for the Source/Sink/Connector deployers doesn't include the partial view information:
Ex:

create or replace materialized view kafka."existing-topic-1$test" as select * from kafka."existing-topic-2";

yields {{name}} == "kafka-database-existing-topic-2"

If you have many partial views on the same topic, it won't be unique. Imagine the case of setting a specific consumer group for each source, it would need to be unique to this pipeline

[ryannedolan]

yields {{name}} == "kafka-database-existing-topic-2"

It should yield kakfa-database-existingtopic2-test. Maybe we broke that? I bet I broke it when I changed K8sMaterializedViewDeployer.

[ryannedolan]

I think partialViewName is a bit leaky, since the planner doesn't otherwise know about partial views. Could we get away with pipelineName here?

For the intended use-cases (e.g. consumer groups, client IDs, etc), can they just use the full pipeline name, e.g. kafka-database-existingtopic1-foo?

[ryannedolan]

Sorry for sending you around in circles. Make sense, thanks.