Paging support in mobile StoreLists

[Eric Durocher]

#12936 addresses the case of long mobile lists at the base level, by adding/removing list items in the DOM to reduce the number of nodes that the browser must layout. This solution is efficient in terms of speed, but not in terms of memory since all the list items must be created upfront.

To go further, it would be nice to also create another mixin that would use the store's paging mechanism to only query the store items that must be displayed at a given time. Both solutions could actually be combined, so that as more and more items are loaded from the store, the number of DOM nodes actually added to the DOM does not grow too much.

[dylan]

Given that no one has shown interest in creating a patch in the past 2+ years, I'm closing this as patchwelcome.