JobScheduler should consider exit codes from PowerShell jobs

Current Situation

• An exit code that is caused by a PowerShell job is not considered by JobScheduler, i.e. an order in a job chain would proceed with subsequent nodes.
• The following job shows the problem:

  <job  order="yes" stop_on_error="no" process_class="Agent_01">
      <script  language="powershell">
          <![CDATA[
  exit 5
          ]]>
      </script>
  
      <run_time />
  </job>
  

• No exit code is reported independently from use of the Windows statement "exit 5" or use of the PowerShell function "exit(5)".
• This problem applies to standalone jobs and to jobs used in a job chain.

Desired Behavior

• Exit codes from PowerShell jobs should be considered in the same way as for shell jobs.