JobScheduler Universal Agent: HTTP tunnel replaces RPC TCP connections

Currently a job with the Agent is started after a http call to the tcp port of the Agent.
Then the Agent starts a process which connects back to the master JobScheduler by tcp and makes rpc (COM) calls.

To replace this second connection by http, the following items need to be implemented: (under construction)

• Master JobScheduler setting to refuse/enable connection if a certificate is not trusted in case of https
• remove Agent task process callback to Master JobScheduler
• make Agent task process callback to Agent main process, instead
• Agent main process bridges communication between Agent task process and master JobScheduler, wraps com calls into http