Manual DAG runs cause `prev_data_interval_start_success` and `prev_data_interval_end_success` to behave unexpectedly

### Apache Airflow version Other Airflow 2 version (please specify below) ### What happened Using Airflow Version 2.4.2 Manually triggered DAG runs interspersed between scheduled DAG runs cause the scheduled DAG runs' [template variables](https://airflow.apache.org/docs/apache-airflow/stable/templates-ref.html) — in our specific use case, `prev_data_interval_start_success` and `prev_data_interval_end_success` — to no longer behave as expected. This appears to be due to how Airflow determines a previous DAG run. When we have mixed manually triggered and scheduled DAG runs, the `logical_date` are not equivalent - For manually triggered DAG runs, the `logical_date` is the exact timestamp the DAG was triggered. The following table shows mixed manually triggered and scheduled DAG runs, and some of the templated timestamps. Notice that this table is ordered by the `Actual execution date`, which is the exact timestamp the DAG executed, and that the `logical_date` is out of order for manually triggered DAGs. _**Bolded italics**_ are the template variables that IMO do not behave as predicted: | DAG Run | Triggered | `logical_date` | Actual execution date | `data_interval`<br />`_start` | `data_interval`<br />`_end` | `prev_data_`<br />`interval_`<br />`start_success` | `prev_data_`<br />`interval_`<br />`end_success` | | ------- | --------- | ------------- | --------------------- | --------------------- | ------------------- | ------------------------------------ | ---------------------------------- | | 1 | Scheduled | 1:05:00 | 1:10:29 | 1:05:00 | 1:10:00 | None | None | | 2 | Manual | 1:11:26 | 1:11:26 | 1:05:00 | 1:10:00 | 1:05:00 | 1:10:00 | | 3 | Scheduled | 1:10:00 | 1:15:00 | 1:10:00 | 1:15:00 | …