Determine shape (or lack of) for selection APIs

[kyleve]

Right now selection for items in the list is modeled on the Item level, and pushed down through to the collection view. While it is nice to leverage collection view's selection behaviour, it does move us away from having a single source of truth to drive UI state. Should we remove selection as a first class item in the Item API, and instead allow consumers to implement their own version?