Add tasks state command to airflowctl

[hyungryuk]

• Add TaskInstancesOperations to operations.py and wire task_instances property in client.py
• Add task_state command to new task_command.py that calls GET /api/v2/dags/{dag_id}/dagRuns/{dag_run_id}/taskInstances/{task_id} and outputs {"state": ...} via AirflowConsole
• Wire airflowctl tasks state --dag-id --dag-run-id --task-id in cli_config.py
• Add taskinstances get help text to help_texts.yaml and integration test to test_airflowctl_commands.py

• related: [AIP-94] airflowctl tasks: add state command #66174

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

[boring-cyborg]

Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide
Here are some useful points:

• Pay attention to the quality of your code (ruff, mypy and type annotations). Our prek-hooks will help you with that.
• In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example Dag that shows how users should use it.
• Consider using Breeze environment for testing locally, it's a heavy docker but it ships with a working Airflow and a lot of integrations.
• Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
• Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
• Be sure to read the Airflow Coding style.
• Always keep your Pull Requests rebased, otherwise your build might fail due to changes not related to your commits.
  Apache Airflow is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: dev@airflow.apache.org
  Slack: https://s.apache.org/airflow-slack

[henry3260]

Thanks for your PR!
Could we add corresponding tests to cover this feature?

[henry3260]

I think we should add a try-except block to catch errors.

[hyungryuk]

@henry3260 Thanks for reviewing my PR!
I believe this is already handled by the safe_call_command function. It captures server error messages and prints them out as shown in the attached image.

[hyungryuk]

Thanks for your PR! Could we add corresponding tests to cover this feature?

No problem! I've just added the tests to cover this feature. Let me know if they look good to you.

[parkhojeong]

i checked term usage :)

[hyungryuk]

i checked term usage :)

@parkhojeong Appreciate that! Thanks for checking.

[justinpakzad]

This appears to be an unrelated change. You might need a rebase (:

[hyungryuk]

Thanks. Just rebased it and cleaned up the commits.

[parkhojeong]

This looks like a useful feature!

[parkhojeong]

I think mapped task instances are currently missing from this implementation.

A task instance is not always identified only by (dag_id, dag_run_id, task_id). For mapped tasks, map_index is also part of the identity, and the public API exposes a separate mapped task instance endpoint for that case.

As implemented, airflowctl tasks state can only query non-mapped task instances, so users have no way to get the state of a mapped task instance through this command. This also means it does not match legacy airflow tasks state, which supports --map-index.