The UI refactor

[johnaohara]

Architecture

• Remove redux state management  #899
• pull UI state into top-level components #900
• create unit tests for UI #901
• create end-to-end tests for UI #902
• Review Error handling in the UI #1130
• UI workflow should be revisited to improve UX and UI code structure #314
  • Maintain context while navigating the web UI #823
  • Improve usability of button navigation in web UI #824
  • Make async processing a "top level" component of the UI #905
  • Dataset filtering should use the patternfly design recommendation #1346

Fixes

• Trying to rerieve a run that does not exists return unfriendly error message #839
• Migration react-router-dom 5 to 6 #723
• Migration Patternfly 4 to 5 #714
• Bar charts missing from "Views" dataset comparison view #744
• Create RLS exception mapper to provide meaningful error messages to User #406
• Remove external hosted JS for Monaco Editor #364
• Replace Monaco editor with patternfly react code editor #903
• Filtering Tests with multiple filtering metrics are unmanagable #960
• Evaluate experiment button visibility. #1077
• Upgrade "@types/react" to "18.2.0" #1215
• Remove UI dependencies on @patternfly/react-table/deprecated #1369
• The Add Action UI could be made more easily usable #1532
• Scrollable list of Schema Label names.  #1635

Features

• When label values are being recalculated, the dataset view should display a warning instead of blank field #873
• Add hover effect on nav elements #826
• Add ability to filter runs for delete #756
• Notify users when thier data has been processed #751
• Link changes chart datapoints to dataset. #360
• introduce fingerprints in a few change detection parameters #349
• When label values are being recalculated, the dataset view should display a warning instead of blank field #873
• Horreum Report Component ordering. #616

[willr3]

We should also remove the filtering and metric boolean attributes from labels and change the UI. The UI currently loads each filtering metric into a select with a drop down for each value. I think it would be easier for users if filtering was first a select of label names then the filtering option changes depending on the value type of the filter. Integers would do well to support a range, strings could support a select or multi-select.