[portaljs/components] Tidy API and docs of the components

[olayway]

Acceptance

• all the components stories are reviewed and components props are documented clearly
• hide BucketViewer for now as not really usable
• hide OpenLayers one as we're using a new Map component
• unify components data-passing API to allow for passing only data prop (no csv, url, or rawCsv), which would have the following interface (or similar)

interface DataProp {
    url?: "string";
    values?: Array<number | string>,
    csv?: "string"
}

Notes / Shaping

Tasks:

• 🚧 go through all the components' stories and add missing field descriptions and enhance existing ones, making it super-clear on how to use them
• (maybe) deprecate the Table component as I've heard

data argument: Multiple names - Situation + Problem + Solution

• (maybe) tidy up the API just a bit: e.g. some components allow for passing either csv OR data OR url props, some allow for passing data that can be either of those three things, some allow for passing rawCsv (instead of csv)
  • Solution A: use only one data prop in all those components that can take in either csv string or url or data array
  • Solution B: use csv, url, data props in all those components

NB: mostly what we are doing is just wrapping an existing library so that it can be used in DataHub ...

e.g. already have ReactVega but we modify it a litle ...

• What do we modify it ...

In terms of design:

• If i were building a component

// data is preparsed in a nice form ...
Table(data=...)
Chart(data=...)

Usage

mydata = loadAndParseCsv(pathToCsv)
Table(data=mydata)
Chart(data=mydata)

But for markdown we don't have this option ... and we need to wrap ...

TableForUseInMarkdown(data={table: ...})
TableForUseInMarkdown(data={url: ...})

[olayway]

@demenech any progress here? :)

[demenech]

PR: #1103

CC: @olayway

[olayway]

FIXED