Add ability to manually trigger reschedule

[jaserud]

Detailed Description

• if scheduler doesn't receive any messages (because some thing is wrong in the system), it will not set any runs to INITIALIZING which means no runs will start
• depending on the problem, scheduler still might not have any messages to trigger it even after every thing is fixed
• we should have a manual way to trigger scheduler for scenarios where it needs to triggered manually

Possible Implementation

• add a POST endpoint to scheduler to trigger reschedule

[Buwujiu]

dev testing is blocked by a graphql query, working on resolving it.

[dahiyaAD]

Link to PRs - 1) https://github.com/icgc-argo/workflow-management-scheduler/pull/29/files 2) https://github.com/icgc-argo/workflow-api/pull/168/files

[lindaxiang]

Tested in QA with Aditya's help:

1. Aditya manually inserted one entry into the postgres database with job state setting as QUEUED
2. Linda called the api endpoint /runs/trigger at: https://wes.rdpc-qa.cancercollaboratory.org/api-docs/ to retrigger the jobs in QUEUED (Now it is returning Runs Triggered Successfully! even though no runs have been re-triggered.)
3. The job was kicked off and showing up running on wes UI

some comments which fall out of the scope but may be the next step:

• Can we request runIds as params to re-trigger specific jobs
• When there are no runs in QUEUED, re-trigger the api endpoint should return informative message to let user know no runs are in QUEUED.

[Buwujiu]

@Buwujiu

1. make tickets for Can we request runIds as params to re-trigger specific jobs.
2. schedule a release for wg-mgmg-scheduler.