Add ability to filter GET /runs by a run name or other information

[golharam]

We are currently implementing the WES API locally using our own database to store run information and we noticed a discrepancy. Currently the definition for GET /runs is to return all the runs the WES API is aware of. In our database, this would mean every run submitted through POST /runs. Today, that may be 10 runs. Tomorrow 100 runs. In a year, 1 million runs. In 2 years 2 million rus.

When we make a call to GET /runs, we only want to find specific named runs and not necessarily fetch every run. We didn't notice any filtering support for fetching runs. The spec does allow for “tags” in the RunRequest object, which clients can include as metadata, but filtering by those tags is not standardized in the spec.

So my question is, what would be the ideal we can enable filtering for runs by run name?

[JaeAeich]

I would also expect filtering based on text search on the name and logs of the workflow and tasks, I think that would be useful from user POV.