[FLINK-33500][Runtime] Run storing the JobGraph an asynchronous operation

[zhengzhili333]

What is the purpose of the change

Currently, submitting a job starts with storing the JobGraph (in HA setups) in the JobGraphStore. This includes writing the file to S3 (or some other remote file system). The job submission is done in the Dispatcher's main thread. If writing the JobGraph is slow, it would block any other operation on the Dispatcher.

Brief change log

• The dispatcher put JobGraph asynchronously in ioExecutor
• The dispatcher write To ExecutionGraphInfoStore asynchronously in ioExecutor
• The JobGraphWriter interface class adds a putJobGraphAsync method for asynchronous write operations
• Implementation class DefaultJobGraphStore adds the putJobGraphAsync method for asynchronous write operations

Verifying this change

This change added tests and can be verified as follows:

• Added the Dispatcher JobSubmission test, use ZooKeeperStateHandleStore as JobGraphStore
• Added the Dispatcher JobSubmission test, use KubernetesStateHandleStore as JobGraphStore

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: (yes)
• 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)

[flinkbot]

CI report:

• 3adc2dc29adf011c2104f5b6ba64ad3fbc3407c2 Azure: SUCCESS

Bot commands

The @flinkbot bot supports the following commands:

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