Speed up retrieval of the JobScheduler Universal Agent status

Current Situation

• The Agent start script provides the operation: ./jobscheduler_agent.sh status
• This operation makes use of Java to send a status request to the Agent and to retrieve the result
• Loading Java for this purpose creates some overhead in time (approx. 3s) and resources (memory)

Desired Behavior

• Use tools with a smaller footprint to retrieve the Agent status, e.g.
  • curl http://localhost:4445/jobscheduler/agent/api
• The start script checks if If curl is available and otherwise falls back to using Java
• Any of the web service URLs as stated with JS-1480 can be added to the web service URL for status retrieval, e.g.
  • ./jobscheduler_agent.sh status command results in the URL http://localhost:4445/jobscheduler/agent/api/command
  • ./jobscheduler_agent.sh status task results in the URL http://localhost:4445/jobscheduler/agent/api/task
• This improvement should be applied to Unix systems. The behavior for Windows systems should remain unchanged.