feat: Dataset table view

[ChrisBaidoo]

Description

Import Datagrid component from STYLE to view a dataset as a table.

closes #366

Checklist:

Put an x in the boxes that apply to this pull request (you can also fill these out after opening the pull request). If you're unsure about any of these, don't hesitate to leave a comment on this pull request!

• [x] I have read the gliff.ai Contribution Guide.
• [x] I have requested to pull a branch and not from main.
• [x] I have checked all commit message styles match the requested structure.
• [x] My code follows the style guidelines of this project.
• [x] I have commented my code, particularly in hard-to-understand areas.
• [x] I have performed a self-review of my own code.
• [ ] I have assigned 3 or less reviewers.
• [ ] New and existing unit tests pass locally with my changes.
• [ ] I have added tests that prove my fix is effective or that my feature works.
• [ ] My changes generate no new warnings.
• [ ] I have made corresponding changes to the documentation.
• [ ] New database changes have been committed.
• [ ] If appropriate, I have bumped any version numbers.

[github-actions[bot]]

Azure Static Web Apps: Your stage site is ready! Visit it here: https://salmon-meadow-05ee3f103-402.westeurope.azurestaticapps.net

[github-actions[bot]]

Azure Static Web Apps: Your stage site is ready! Visit it here: https://salmon-meadow-05ee3f103-402.westeurope.azurestaticapps.net

[github-actions[bot]]

Azure Static Web Apps: Your stage site is ready! Visit it here: https://salmon-meadow-05ee3f103-402.westeurope.azurestaticapps.net

[cooper667]

We use pagination but only have 1 arrow - assuming this is done automatically? Can we either abandoned pagination for a full scrollable list or increase number of results shown at once (maybe 60?) and add in full pagination arrows?

Regarding this, should we just NOT have pagination as we have always loaded the full dataset (i think) so it's not like we need to implement infinite scroll or anything, we have it all and the pagination is currently artificial? Then maybe add pagination in the future when we actually lazy load the data?

(one for @joshuajames-smith and/or @ChasNelson1990 and/or @ChrisBaidoo )

[joshuajames-smith]

We use pagination but only have 1 arrow - assuming this is done automatically? Can we either abandoned pagination for a full scrollable list or increase number of results shown at once (maybe 60?) and add in full pagination arrows?

Regarding this, should we just NOT have pagination as we have always loaded the full dataset (i think) so it's not like we need to implement infinite scroll or anything, we have it all and the pagination is currently artificial? Then maybe add pagination in the future when we actually lazy load the data?

(one for @joshuajames-smith and/or @ChasNelson1990 and/or @ChrisBaidoo )

Last spoke to @ChasNelson1990 I believe something was mentioned how pagination is good for E2E? But from my POV im happy with full data load with scroll - this is supported by the filter/search system anyway!

[github-actions[bot]]

Azure Static Web Apps: Your stage site is ready! Visit it here: https://salmon-meadow-05ee3f103-402.westeurope.azurestaticapps.net