List management

[tdudgeon]

We need to allow the user to curate lists of favourite records. In other applications like this this is often termed list management or cherry picking.

The card view is key to this, though in future the functionality could be exposed through other components.

1. The user should be able to create any number of named lists. Initially there is one list named default that has no members.
2. Only one list can be active at any time.
3. A list contains only record IDs and the dataset from where they came.
4. A component can optionally indicate whether the item is in the current list or not.
5. A component can optionally allow to change whether the item is in the current list or not.
6. In the case of the card view the above 2 can be handled as a checkbox in the header of the card.
7. Switching between lists, defining new lists and deleting lists would be done in a List management panel of the settings popup. This should be treated as a new component that can be added to any mini-app.
8. List operations can be performed in the list management panel e.g. create new list which is the intersection of 2 lists (this is not needed initially).
9. It should be possible to load records of a dataset belonging to a particular list.
10. Lists do NOT form part of the application state but are saved separately (this needs further thought).
11. Once the data tier exists the lists should be saved along with the data sets do that they can be used in data transform operation.
12. For any new mini-app it should be possible to just "enable" list management and it just works as the relevant components will be list management aware.