[Feature][Manager] Support schedule instance callback to submit Flink batch job

[aloyszhang]

Description

The whole procedure for offline jobs is

An InLong group of the offline type is created and approved, and then, the scheduling engine client will register schedule info to the scheduling engine(support built-in quartz engine and third-party engines).

The scheduling engines will generate instances periodically, every instance means the offline sync should execute once.

By now, we have already supported the management of schedule info like configuration/register, etc.

The only remaining part is the scheduling instance's callback to submit a Flink batch job to Flink service.
This part is marked with yellow color in the draw above.

We should implement this part to complete the processing of offline sync jobs.

Use case

Support schedule instance callback to submit Flink batch job

Are you willing to submit PR?

• Yes, I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct