Add CLI support for bulk pause and resume of DAGs

[shahar1]

closes: #36956

This PR adds the ability for airflow dags (un)pause commands to treat dag_id as a regex (similar to backfill), so we could apply it to multiple DAGs.

---

^ 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.

[shahar1]

Following @eladkal's comment in #36994, I added a confirmation prompt to avoid accidental (un)pausing. I also formatted the output with AirflowConsole().print_as to make it easier to read.

[ephraimbuddy]

It seems like unpausing a single dag is now broken by this PR. I have not tested bulk pause/unpause but for one dag, it seems broken

Ok. It now errors when the dag is paused and you are pausing again. I think it should just exit without error if DAG is already paused

[shahar1]

It seems like unpausing a single dag is now broken by this PR. I have not tested bulk pause/unpause but for one dag, it seems broken

Ok. It now errors when the dag is paused and you are pausing again. I think it should just exit without error if DAG is already paused

Apologies for the confusion, maybe raising an error for pausing an already paused dag (and vice versa) is indeed too aggressive - I'll try to come up with a fix later on.

[ephraimbuddy]

It seems like unpausing a single dag is now broken by this PR. I have not tested bulk pause/unpause but for one dag, it seems broken
Ok. It now errors when the dag is paused and you are pausing again. I think it should just exit without error if DAG is already paused

Apologies for the confusion, maybe raising an error for pausing an already paused dag (and vice versa) is indeed too aggressive - I'll try to come up with a fix later on.

Added the change here: #38585. Take a look when you have time