Optimize the flink EngineConn and enhance the operator capabilities of ECM module and EC module.

[wushengyeyouya]

What is the purpose of the change

Optimize the flink EngineConn and enhance the operator capabilities of ECM module and EC module.

Brief change log

(for example:)

• Resolve the problem of fetching progress with no information.
• Resolve the problem of deploying flink application without yarn appId.
• Enhance the FlinkOnceJob, support to execute set, show grammar of flinkSQL.
• Enhance the FlinkOnceJobTest, add the support of using onceJob operators.
• Since both ECM and EC need Operator module, so the Operator module has been moved to linkis-manager-common.
• Add the capability of Operator to ECM, so LinkisManager can request to execute ECM Operators by RPC.
• Add the capability of fetch EC logs from ECM, now we can get all logs of all ECs whenever the EC is running or stopped.
• Optimize the architecture of LinkisManager, so linkis-computation-client can request LinkisManager to route operator request to ECM.
• Optimize the logic of EC creation, and fill in more EC information when EC is creating.
• Delete the EngineConnLogOperator in accessible-executor, since some errors will be throws when the EC is starting or stopped.
• Add the capability of executing Operators to ECM in linkis-computation-client.

Verifying this change

(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

• Added tests for submit and execute all kinds of jobs to go through and verify the lifecycles of different EngineConns.

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

• Dependencies (does it add or upgrade a dependency): (yes / no)
• Anything that affects deployment: (yes / no / don't know)
• The MGS(Microservice Governance Services), i.e., Spring Cloud Gateway, OpenFeign, Eureka.: (yes / no)

Documentation

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

[peacewong]

LGTM.