IssueTracker

When there are long running workers which are run multiple times a day, there's a lot of history of these completed workers in the WorkManager database. And the workManager api which lets us query the workInfo's looks something like this -

`workManager.getWorkInfosForUniqueWorkLiveData(TAG)`

The pain point with this is that this gives you all the completed workers' workInfos as well. If the intention is only to observe the status of the currently running workers, it requires a call to pruneWork() which seems like an anti-pattern. A work around with the current apis would be to create unique tags for each work but then again that's a pain to maintain if you have a complicated use case.

What I propose is a builder method along with this api to be able to put in simple filters like status of the worker(BLOCKED, ENQUEUED, RUNNING, SUCCEEDED) to begin with. Have got a thumbs-up from Rahul Ravikumar from the Toolkit team on this.