ui: table - implement component/module

[christophercr]

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  
[X] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead see https://github.com/NationalBankBelgium/stark/blob/master/CONTRIBUTING.md#got-a-question-or-problem

Expected behavior

Separate module including component(s), styling and all the API related to this feature.

The stark-table should support the following features already supported in Stark 9:

• Nested objects
• Custom formatted values
• Translated values
• Translate headers (ui: table - add support for translated column headers #955)
• Selection (single and multiple) (ui: table - add support for row selection (single and multiple) #880)
• Sorting (single and multiple columns)
• Filtering (globally and per column) supporting wildcards
• Pagination (ui: table - implement pagination support (live and offline modes) #521)
• Show/hide columns (minimap) (ui: table - allow to show/hide columns on demand #522)
• Table action bar (ui: table - implement table and row action bars #512)
• Row action bar (ui: table - implement table and row action bars #512)
• Custom row styling (ui: table - add support for customizing styles (header, column, row and cell) #523)
• Custom header styling (ui: table - add support for customizing styles (header, column, row and cell) #523)
• Custom cell styling (ui: table - add support for customizing styles (header, column, row and cell) #523)
• Custom column styling (ui: table - add support for customizing styles (header, column, row and cell) #523)
• Click callbacks (on selection and on row) (ui: table - add support for click/touch callbacks #795)
• Message when no data is loaded (pristine)
• Message when data is empty
• Switch to cards view on mobile
• Fix headers on the page (ui: grid - keep the top of the list fixed when scrolling down #196)

What is the motivation / use case for changing the behavior?

See #104