Wordpress-android: Add Filtering and Searching to Blog Posts List

[theck13]

Add filtering and searching to the Blog Posts list including Published, Draft, Scheduled, and Trashed. See the mockups below for illustration.

Along with a complementary issue for Site Pages, this will fix https://github.com/wordpress-mobile/WordPress-Android/issues/62, https://github.com/wordpress-mobile/WordPress-Android/issues/4693, and https://github.com/wordpress-mobile/WordPress-Android/issues/5884.

[nellofn]

This will be a really nice addition.

A user asked how to go about finding trashed content on Android for its self hosted site (1316298-zen).

[rezzap]

Another user asked for this in 1595629-zen.

[thehenrybyrd]

We've had another request for this in 1645933-zen.
This seems like more than a really nice addition - for anyone who has more than, say, 10 posts, it will make managing post _much much easier_.
Going from Pages, where we already have filtering and searching, to Posts, where we don't, is rather surprising. In addition, iOS already has this, so adding it to Android would be a nice parallel.
I'd love to see this added to Posts as well!

[SiobhyB]

This comes up frequently in the app reviews. An example from a recent three star rating:

Quite nice. Unfortunately it is not possible to sort the posts, for example drafts/published or the oldest post first. This makes it hard to find drafts which are some months old, because there is no search option. I would be happy to rise the rating, if the app gives me the features above in future. Thanks for your work.

[charliescheer]

Another request from #1672607-zen

[thehenrybyrd]

Here's another in #1678733-zen

[SiobhyB]

Another request from a four star review:

An app almost excellent for managing a blog and to follow others, only negative note: the drafts are mixed with the articles already published.

[thehenrybyrd]

Another where a user would like to restore a trashed post. Without the ability to view trashed posts, they can't be restored from the app. #1749484-zen

[oguzkocer]

Closing this in favor of #4693 and #62 since we'll work on each feature separately.

Note for HEs: These issues are now a part of a project that's starting as of today, so it shouldn't be too long before they are implemented.