filter by multiple statuses in BulkActionsFilter

[jamiedemaria]

Summary & Motivation

You can select multiple statuses when you filter for runs in the UI, so we should support filtering backfills for multiple statuses. Alternatively we can wait until the dagster run status for a backfill is stored in the DB and then just allow filtering for multiple statuses of dagster run statuses

companion internal pr https://github.com/dagster-io/internal/pull/11113

How I Tested These Changes

unit tests

[jamiedemaria]

• Reorder status and filters params for get_backfills #23773
• filter by multiple statuses in BulkActionsFilter #23772 👈
• BulkActions filters in GQL layer #23682
• create time filtering for bulk actions table #23560
• Graphene layer for serving the Runs Feed #23375
• 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-gh69hjumo-elementl.vercel.app
https://jamie-statuses-plural-filter.core-storybook.dagster-docs.io

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

[jamiedemaria]

@prha @sryza The main thing with this PR is if this is even worth adding.

We can filter runs by multiple statuses, so we want to be able to filter backfills by multiple statuses. But we filter runs by DagsterRun statuses, so that's the status we'll eventually filter backfills by.

I was thinking it could be useful to also allow filtering backfills by multiple BulkActionStatuses to enable us to do non-performant filtering before we store the dagster run status in the DB, but it might not really be worth it

Related - I'm wondering if we should have a more verbose name for the statuses attr to disambiguate the bulk action status from the dagster run status

[prha]

I think we should go more aggressively.

We should deprecate status and error if they provide both status AND filters