DAGs with future `start_date` are automatically marked as success without executing tasks

### Body

For the following DAG:

```
from datetime import datetime

from airflow import DAG
from airflow.operators.bash import BashOperator

default_args = {
'owner': 'airflow',
}

with DAG('my_future_dag',
default_args=default_args,
start_date=datetime(2050, 1, 1),
schedule="@daily",
catchup=False
):
BashOperator(task_id="task1", bash_command="echo 1")
BashOperator(task_id="task2", bash_command="echo 2")
BashOperator(task_id="task3", bash_command="echo 3")
BashOperator(task_id="task4", bash_command="echo 4")
```

As expected no runs will be started till 2050 but I might still want to manually invoke runs. Trying to do so will result in DAGRun marked as success and no tasks being executed as can see



However changing the `start_date` to `datetime(2023, 1, 1)` then tasks are executed as expected for manual runs:

**The bug:**
tasks should be executed for manual runs. The current case where dagrun is marked as success but no tasks are running or reporting failure is wrong.

By the way, a very interesting thing to explore is that if you first deploy the dag with `datetime(2023, 1, 1)` then change it to `datetime(2050, 1, 1)` Airflow has no problem with running tasks with that `start_date`:



### Committer

- [X] I acknowledge that I am a maintainer/committer of the Apache Airflow project.