Non-table layout for the paginated search mixin

[alancleary]

The paginated search mixin displays results via a configurable table. Since this table is configurable at run-time, it is a flexible approach that allows users to customize the results layout to their specific needs without forking the project. However, the table is not very compact and can be visually cumbersome when there's many fields and/or there's fields with large content. Although the table configuration can be used at run-time to effectively display search results in a more compact non-table format, this workaround requires users to heavily integrate display code with the data they're giving the component. More generally, this is tedious to implement and clutters the user's code.

For these reasons, the paginated search mixin should be extended to provided an alternative to the table layout that is configurable using the same resultAttributes, tableHeader, and tableColumnClasses properties, although these property names should be changed to be not specific to the table layout.

I'll use this as the catalyst to finally create a spec for paginated search and we can flesh out the details of the non-table results layout there. It's worth noting now, though, that this non-table display still needs to be generic enough to be used in many contexts so the bespoke arrangement of fields for specific searches is out of scope.