Description
Tasks can be sent to the entrance only when the execution node status is complete or running

Description
add ecm health check when select available node to execute task

Here are some easy-to-fix issues or feature:
#1160 [Bug] NPE in CsJobListener
#1159 [Bug] Add JAVA_HOME for ProcessEngineConnLaunch
#1158 [Bug] NPE of api '/linkisManager/rm/engines'
#1157 [Bug] Shell engine will not append shell-stdout into persisted-log
#1151 [Featrue] Optimize the login user association limit of the query results of the datasource/dbs http interface
#1144 [Bug] The engine will not automatically exit when it is in the starting state
#1143 [Bug] Cannot be processed when the submitted task script is empty code
#1142 [Feature] Task submit with ECM health check

Describe the bug
Shell engine will not append shell-stdout to the persistent log when executing

Expected behavior
When the Shell engine is executed, shell-stdout needs to be appended to the persistent log

Screenshots

Describe the bug
In some scenarios, org.apache.linkis.cs.server.scheduler.impl.CsJobListener#onJobCompleted,the job errorResponse may be null

Expected behavior
Only consider that errorResponse is not empty
Screenshots

Describe the bug
When get engine nodes include node EMnode was empty will cause NullPointerException

Expected behavior
When it is empty, record map does not store this attribute

Screenshots

Describe the bug
ProcessEngineConnLaunch#initializeEnv should add JAVA_HOME

Screenshots