Pull scheduler logic out of asset classes

[uranusjr]

Body

The SDK should contain no database-related code, but currently the scheduler uses the evaluate function to check if an asset dependency is “ready”, which involves hitting the database in some cases. We should move it into Airflow core.

The best way to do this is probably similar to how DAGs are turned into SerializedDag. We should create a class in core Airflow to represent BaseAsset subclasses, and put logic there.

Committer

• I acknowledge that I am a maintainer/committer of the Apache Airflow project.

[JASNOTJAZZ]

To fix this, we should move this logic into Airflow core by creating a new class that handles BaseAsset subclasses.

This keeps the SDK clean while ensuring database interactions happen only where it should

[uranusjr]

PR ready: #47484