Use new ListResources in the webapi layer for pagination and filtering

[kimlisa]

part of RFD 55

Description

In addition proccess query params sent in with request

Before Merge

• Requires webassets update with corresponding changes (or else the web UI list views will be inaccurate)
• Mark RFD 55 state from draft to implemented

[zmb3]

Just a couple minor comments.

[espadolini]

Nothing to add

[kimlisa]

May i get a review for this commit please from either @zmb3, @espadolini, or @rosstimothy: 584feaa

The web UI needed a flag that would tell it if the list is empty from filter results, or if user just didn't have any resource to access. These are the views depending on this flag and list results:

1. If a list result was empty, and user had no resources to access, and the user has read + write access then the UI will show the user how to get started:
   

2. If a list result was empty, and user had no resources to acces, and the user has read only access then we show this screen:
   

3. If a list result was empty, and user HAS resources to access, then it means there was no results found after applying filter (we have a bookmarkable url feature that saves the filter queries, so on first load it can be empty b/c of no results):
   

[espadolini]

@kimlisa in a hypothetical future in which we can do filtering in the backend itself that extra flag would force us to still figure out if something else could've been available - wouldn't it be simpler to only show the getting started UI element if the filter textbox is empty?

[kimlisa]

@kimlisa in a hypothetical future in which we can do filtering in the backend itself that extra flag would force us to still figure out if something else could've been available - wouldn't it be simpler to only show the getting started UI element if the filter textbox is empty?

i think you're right @espadolini, it's also weird that we are ignoring the filter field too (in the UI b/c it will get replaced with the empty state), reverted