[ui] Always launch using pure asset backfills except on asset job pages

[bengotow]

Related: https://linear.app/dagster-labs/issue/FE-499/launch-all-non-asset-job-runs-using-pure-asset-backfill-path

Summary & Motivation

We are switching from many hidden asset jobs to just one which does not have a predefined partition set (this has already merged). We are currently launching assets incorrectly because the new singleton-hidden-asset-job does not have a pipeline partition set definition, which prevents the UI from launching single runs of partitioned assets.

This PR explores launching ALL non-asset-job runs for assets as pure-asset backfills endpoint (the launchBackfill mutation with an assetSelection.

This is much simpler, and it does work (though you always get a backfill currently), BUT:

• There is no way to provide config (previously shift-clicking would give you the launchpad)
• There is no way to indicate whether to include checks (previously a checkbox inside the launchpad)
• There is no way to launch a backfill using a single run and a partition range specified in tags
• There is always a backfill created (though this seems fixable)

Curious to get thoughts on this direction @sryza

It seems like we could use the new singleton-hidden-asset-job for unpartitioned assets with config, but I can't think of a way to allow execution of a single partition of a partitioned asset with config.

[github-actions]

Deploy preview for dagit-core-storybook ready!

✅ Preview
https://dagit-core-storybook-n7zgs5v7n-elementl.vercel.app
https://bengotow-2024-08-FE-499.core-storybook.dagster-docs.io

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

[sryza]

There is no way to provide config (previously shift-clicking would give you the launchpad)
There is no way to indicate whether to include checks (previously a checkbox inside the launchpad)

Would it make sense to still honor the launchpad if they force it?

There is no way to launch a backfill using a single run and a partition range specified in tags

This seems fine. We should be deciding whether to launch a single run or multiple runs based on the BackfillPolicys, not based on anything set in the frontend.

There is always a backfill created (though this seems fixable)

Yeah we can fix this on the backend if we want to.