[ui] Use RunFeed table for all remaining Runs views

Open bengotow opened this issue 1 year ago • 1 comments

Summary & Motivation

This PR swaps out the old RunTable for the new RunFeedTable for users with the new runs feed feature flag:

On the sensor page
On the schedule page
On the global AMP page and the AMP sensor page
On the Asset > Auto-materialize page [note: it now has checkboxes and the Actions button]
On the job runs page

Cleanup:

I moved a bunch of existing stuff into smaller files to re-use it and there aren’t significant changes in these files:

<RunsFeedError />
<PipelineRunsEmptyState/>
useIncludeRunsFromBackfillsOption
useRunsFeedEntries

One sidenote is that I kept a separate top level component for PipelineRunFeedRoot instead of trying to unify it with the global runs root, mostly because the global one has tabs, and the run-scoped one has “locked” tags. They are /just/ different enough that I think composition is better than a bunch of props turning things on and off. The other pages (eg: sensor, schedule runs) all use a new <RunsFeedTableWithFilters />

How I Tested These Changes

I took screenshots before and after of each impacted page to verify there weren't unintended changes, etc. However, there are a few places where an additional column is present in the new UI because our old tables were inconsistent. I think this is preferable and run tables should look the same everywhere, but I'll confirm with @braunjj.