[FLINK-39491][runtime] move lineage Listener creation to Dispatcher

[HuangZhenQiu]

What is the purpose of the change

Currently, the job creation event happens in client side, and any follow up status change events propagation happen in DefaultExecutionGraph. In this case, there are two instances of the same job listener created. We probably may consider moving the job creation event to dispatcher. With the change, a single job listener instance for each type in JVM needs to be created. Then, states within the instance will be shared within the whole job lifecycle.

Brief change log

• Move JobStatusChangedListener creation for Job Creation Event to Dispatcher
• Change JobStatusChangedListener to singleton for each type in JobStatusChangedListenerUtils
• Add test cases for JobStatusChangedListenerUtils.

Verifying this change

This change added tests and can be verified as follows:

• JobStatusChangedListenerUtilsTest is added to test JobStatusChangedListener creation

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

• Dependencies (does it add or upgrade a dependency): (no)
• 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? (no)
• If yes, how is the feature documented? (not applicable)

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)

[flinkbot]

CI report:

• 05af321 Azure: SUCCESS

Bot commands

The @flinkbot bot supports the following commands:

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

[HuangZhenQiu]

@flinkbot run azure

[HuangZhenQiu]

@flinkbot run azure