[AIP-94] Mark dags state and next-execution CLI commands as migrated to airflowctl

[YAshhh29]

Add the @deprecated_for_airflowctl marker decorator to two dags CLI
commands whose airflowctl equivalents already exist:

• dags state → airflowctl dags state
• dags next-execution → airflowctl dags next-execution

Both airflowctl commands are already implemented and registered in
airflow-ctl, so functional parity is met. This follows the same
marker-only direction as #68932 (variables), #68958 (config), and
#68650 (dags pause/unpause).

related: #68402

[potiuk]

LGTM — verified both replacement strings against the airflowctl registry (dags state / dags next-execution); no-op marker, no drift.

One thing before this can merge: the branch currently has conflicts with main (mergeable: dirty). Please rebase on the latest main and resolve the conflict.

[YAshhh29]

Thanks a lot for the review, @potiuk!

Rebased on the latest main and resolved the conflict in test_command_deprecations.py — kept both dag_list_import_errors from #68602 and the two new entries (dag_state, dag_next_execution). The diff is still the same 4 lines added.

Also, since this is one of my initial contributions to Airflow, I'd love any feedback on things I can improve - whether that's PR structure, commit message style, testing approach, or anything else. Happy to iterate.

[YAshhh29]

Rebased again to pick up the newer entries from #68972 (connections) and #68650 (dags pause/unpause/list-dag-runs). No functional change on my side — still the same 2 lines in dag_command.py + 2 lines in test_command_deprecations.py.

[YAshhh29]

Gentle bump — this has been approved and green for a week. Happy to rebase again if it helps.

[henry3260]

Appreciate your contribution!

[github-actions]

Backport failed to create: airflow-ctl-v0-1-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
❌	airflow-ctl-v0-1-test

You can attempt to backport this manually by running:

cherry_picker 5628e83 airflow-ctl-v0-1-test

This should apply the commit to the airflow-ctl-v0-1-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.