### Apache Airflow version

2.2.2

### What happened

Current time 16:54 UTC
Execution Schedule: * * * * *
Last Run: 16:19 UTC
DAG Paused
Catchup=False

`airflow dags next-execution sample_dag`
returns
```
[INFO] Please be reminded this DAG is PAUSED now.
2022-03-22T16:20:00+00:00
```

### What you think should happen instead

I would expect
```
[INFO] Please be reminded this DAG is PAUSED now.
2022-03-22T16:53:00+00:00
```
To be returned since when you unpause the DAG that is the next executed DAG

### How to reproduce

Create a simple sample dag with a schedule of * * * * * and pause with catchup=False and wait a few minutes, then run 
`airflow dags next-execution sample_dag`

### Operating System

Debian

### Versions of Apache Airflow Providers

Airflow 2.2.2

### Deployment

Astronomer

### Deployment details

_No response_

### Anything else

_No response_

### Are you willing to submit PR?

- [ ] Yes I am willing to submit a PR!

### Code of Conduct

- [X] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)

"""
        Test that CLI respects -I argument
        We just check we call dag.run() right. The behaviour of that kwarg is
        tested in test_jobs
        """
        dag_id = "test_dagrun_states_deadlock"
        run_date = DEFAULT_DATE + timedelta(days=1)
        args = [
            "dags",
            "backfill",
            dag_id,
            "--local",
            "--start-date",
            run_date.isoformat(),
            "--ignore-first-depends-on-past",