Add DataTable component

[virajsanghvi]

Description

This is an attempt at a generic datatable based on https://ui.shadcn.com/docs/components/data-table and implemented by ai. We need to do a better evaluation of what functionality/interface we want and update this, but figured this is a decent start.

Issues Resolved

N/A

Check List

• New functionality includes testing.
• New functionality has been documented.
• All tests pass
  • yarn lint
  • yarn test-unit
• Update CHANGELOG.md
• Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[angle943]

Once we start consuming OUI 2.0, i thiunk we should enable devs in OSD to use tailwind classes. But one concern, why was it decided to use the oui: prefix? What if we just use tw:? (ref: https://tailwindcss.com/docs/styling-with-utility-classes#using-the-prefix-option)

One of the pros of using tailwind is that it appears it is the industry-accepted way of handling css in FE, so this can potentially increase open source community interest. But i fear that oui: will give people second-thought (ie: are these really tailwind classes? Did OUI do something unique to it? If so, where are the docs? ETC)

But if we use tw: prefix, there is less ambiguity i think

[angle943]

i also want the components we build to be highly customizable (style-wise) by consumers if needed, and i'm glad that this PR implemented className.

But i think we should use https://www.npmjs.com/package/tailwind-merge for all of our OUI components. This will allow us to safely override classes

[angle943]

i think we have been using data-test-subj and an optional data-test-subj prop to be able to target our components in tests. Is that a pattern we want to continue supporting with this new OUI version?