JobManagerHandler conversion

[chaen]

Continue the implementation of the /jobs route.
Missing methods are:

• getMaxParametricJobs: no need to implement in the router. The legacy adapter should query the CS directly.
• submitJob(self, jobDesc): started, needs completion (JobParametersDB, JobLoggingDB, etc)
• confirmBulkSubmission(self, jobIDs) : needs larger discussion about ParametricJobSubmission
• rescheduleJob(self, jobIDs): POST to /jobs/{job_id}/reschedule and /jobs/reschedule for bulk
• removeJob(self, jobIDs): Do we need both removeJob and deleteJob ? (If yes, can removeJob be a parameter of deleteJob)
• deleteJob(self, jobIDs): see above
• killJob(self, jobIDs): POST to /jobs/{job_id}/kill and /jobs/kill for bulk (see [1])
• resetJob(self, jobIDs): Could this be a parameter to rescheduleJob?

[1] We could think of having killJob and rescheduleJob react to setStatus(kill) or setStatus(reschedule). We do not because in general, it is forbidden to set an arbitrary status. Kill and Reschedule are exceptions, that's why they have a dedicated API.

[ryuwd]

In addition to a lot of refactoring:

• getMaxParametricJobs: no need to implement in the router. The legacy adapter should query the CS directly.
  • Left this alone (TBD)
• submitJob(self, jobDesc): started, needs completion (JobParametersDB, JobLoggingDB, etc)
  • Left this alone (TBD)
• confirmBulkSubmission(self, jobIDs) : needs larger discussion about ParametricJobSubmission
  • Left this alone (TBD)
• rescheduleJob(self, jobIDs): POST to /jobs/{job_id}/reschedule and /jobs/reschedule for bulk
  • TBD
• removeJob(self, jobIDs): Do we need both removeJob and deleteJob ? (If yes, can removeJob be a parameter of deleteJob)
  • This has become a DELETE operation (DELETE /api/jobs, DELETE /api/jobs/{job_id})
• deleteJob(self, jobIDs): see above
  • This has been removed in favour of single and bulk status change (PATCH /api/jobs/status, PATCH /api/jobs/{job_id/status)
• killJob(self, jobIDs): POST to /jobs/{job_id}/kill and /jobs/kill for bulk (see [1])
  • removed in favour of single job and bulk status change (PATCH /api/jobs/status, PATCH /api/jobs/{job_id/status)
• resetJob(self, jobIDs): Could this be a parameter to rescheduleJob?
  • TBD with rescheduleJob