Store and expose task inlet references to assets
Backend part for #50873.
The name 'consuming dags' is somewhat confusing. This is actually a backref to DagScheduleAssetReference, and as the name suggests, it only tracks dags that reference assets in its schedule, not other ways of “consuming”, namely inlet references. Therefore, I changed the name to scheduled_dags instead, to reflect the fact that those dags actually use the asset for scheduling.
I added a new model TaskInletAssetReference to track inlet references. A backref is also created to expose this to the REST API (so we can later show this in the UI). I’m calling this consuming_tasks, but open to other ideas (again, consuming might not be the best word).
Good point, I’ll add a news fragment file.