[ui] remove run status column on backfills page

[jamiedemaria]

Summary & Motivation

The run status column on the backfills page cannot load for asset-job backfills if the backfill policy of the asset changes. This is because we use run tags/db indices to determine the status of each partition. We need to look for different tags with different backfill policies, but dont store what the backfill policy was when the backfill ran.

Rather than try to make the run status column work, we decided to remove the column for these reasons:

1. job-based backfills are less commonly used and a "secondary" feature. We don't show this run status information for pure asset backfills.
2. there is work being done for jobs to support multiple partition definitions in the future. when that happens, this graphic makes less sense since we'd need to include one bar per partition and that could take up a lot of space.

How I Tested These Changes

[jamiedemaria]

• [ui] remove partition statuses from backfill termination logic #23147 : 2 dependent PRs (#23150 , #23231 )
• [ui] remove run status column on backfills page #23143 👈
• make job backfill status consistent with asset backfill status #23141
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @jamiedemaria and the rest of your teammates on Graphite

[github-actions]

Deploy preview for dagit-core-storybook ready!

✅ Preview
https://dagit-core-storybook-4s7l7mrok-elementl.vercel.app
https://jamie-backfill-page-run-status-column.core-storybook.dagster-docs.io

Built with commit f38de78.
This pull request is being automatically deployed with vercel-action

[jamiedemaria]

@salazarm @bengotow I'd like to note that I'm not very familiar with front end code. I did my best, but definitely could be making some silly mistakes!