[FLINK-38530] create Dynamic Kafka Source for pyflink

[bowenli86]

What is the purpose of the change

create Dynamic Kafka Source for pyflink

Brief change log

• create Dynamic Kafka Source and related py classes for pyflink
• add tests
• upgrade kafka connector dependency 4.0.1-2.0 so it picks up dynamic source java classes, which existing 3.0.0 connector does not have

Verifying this change

This change added tests and can be verified as follows:

• Added test_dynamic_kafka.py

Does this pull request potentially affect one of the following parts:

• Dependencies (does it add or upgrade a dependency): (yes)
• The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
• The serializers: (no)
• The runtime per-record code paths (performance sensitive): (no)
• Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (no)
• The S3 file system connector: (no)

Documentation

• Does this pull request introduce a new feature? (yes)
• If yes, how is the feature documented? (docs)

[flinkbot]

CI report:

• e3126ca Azure: FAILURE

Bot commands

The @flinkbot bot supports the following commands:

• @flinkbot run azure re-run the last Azure build

[bowenli86]

test failures are unrelated

[dianfu]

@bowenli86 Thanks a lot for the work! 👍 Only a few minor comments.

[dianfu]

What about also introducing class StreamPatternSubscriber and KafkaStreamSetSubscriber ?

[bowenli86]

added

[dianfu]

It would be great to also update the documentation here: https://nightlies.apache.org/flink/flink-docs-master/docs/connectors/datastream/dynamic-kafka/

[bowenli86]

found out dynamic kafka doc has been moved to kafka connector repo https://github.com/apache/flink-connector-kafka/blob/main/docs/content/docs/connectors/datastream/dynamic-kafka.md

created a PR there apache/flink-connector-kafka#211

[bowenli86]

(btw, the pyflink kafka connector migration to connector repo which has been left half way done for 2 years is better to be fixed, otherwise we'll be constantly facing the inconsistency among the 2 repos and jump back and forth for all kinds of issues. Do you have time or anyone in OSS or Alibaba can take on it?)