### 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)

args = self.parser.parse_args(
            [
                "dags",
                "trigger",
                "example_bash_operator",
                "--run-id",
                "trigger_dag_xxx",
                "--conf",
                '{"conf1": "val1", "conf2": "val2"}',
                "--output=json",
            ]
        )
        with contextlib.redirect_stdout(io.StringIO()) as temp_stdout:
            dag_command.dag_trigger(args)
            
            out = temp_stdout.getvalue().strip().split("\n")[-1]
        parsed_out = json.loads(out)
        assert 1 == len(parsed_out)
        assert "example_bash_operator" == parsed_out[0]["dag_id"]
        assert "trigger_dag_xxx" == parsed_out[0]["dag_run_id"]
        assert {"conf1": "val1", "conf2": "val2"} == parsed_out[0]["conf"]
    def test_delete_dag(self):