Configure back_populates between DagScheduleDatasetReference.dag and DagModel.schedule_dataset_references

[Taragolis]

We have an annoying warning about conflicts with relationship between DagScheduleDatasetReference.dag and DagModel.schedule_dataset_references

Resetting the DB

DB: postgresql+psycopg2://postgres:***@postgres/airflow
[2024-05-03T09:37:44.023+0000] {db.py:1651} INFO - Dropping tables that exist
[2024-05-03T09:37:44.399+0000] {migration.py:216} INFO - Context impl PostgresqlImpl.
[2024-05-03T09:37:44.399+0000] {migration.py:219} INFO - Will assume transactional DDL.
[2024-05-03T09:37:44.422+0000] {migration.py:216} INFO - Context impl PostgresqlImpl.
[2024-05-03T09:37:44.422+0000] {migration.py:219} INFO - Will assume transactional DDL.
INFO  [alembic.runtime.migration] Context impl PostgresqlImpl.
INFO  [alembic.runtime.migration] Will assume transactional DDL.
INFO  [alembic.runtime.migration] Running stamp_revision  -> 677fdbb7fc54
/opt/airflow/airflow/utils/db.py:133 SAWarning: relationship 'DagModel.schedule_dataset_references' will copy column dag.dag_id to column dag_schedule_dataset_reference.dag_id, which conflicts with relationship(s): 'DagScheduleDatasetReference.dag' (copies dag.dag_id to dag_schedule_dataset_reference.dag_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards.   To silence this warning, add the parameter 'overlaps="dag"' to the 'DagModel.schedule_dataset_references' relationship. (Background on this error at: https://sqlalche.me/e/14/qzyx)
WARNI [airflow.models.crypto] empty cryptography key - values will not be stored encrypted.

Database has been reset

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

[dirrao]

LGTM