Non-transitive sync status

[smackesey]

Summary & Motivation

Internal companion PR: https://github.com/dagster-io/internal/pull/10427

Non-transitive sync status has been behind an org setting and was turned on for several pilot orgs a few months ago. We heard either positive reports on performance impact or nothing. This PR (and its companion) remove the org setting and turn on non-transitive unsynced for everyone.

How I Tested These Changes

Existing test suite.

[smackesey]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• Non-transitive sync status #22797 👈
• Switch DagsterInstance.use_transitive_stale_causes default to False #22806
• master

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

Join @smackesey and the rest of your teammates on Graphite

[gibsondan]

you could alternately leave the setting but start defaulting it to OFF instead of ON (so that if we need to we can re-enable it for specific orgs temporarily). Up to you.

[smackesey]

you could alternately leave the setting but start defaulting it to OFF instead of ON (so that if we need to we can re-enable it for specific orgs temporarily). Up to you.

Thought about it, but I think it's unlikely we'll need to do that, especially with release as part of 1.8

On second thought I think this is a good idea because this could potentially change some sensor behavior (stale_assets_only run requests). I will stack this full removal on a simpler default toggle.