Add task instance management commands to airflowctl CLI

[Suraj-kumar00]

Adds Task Instance management support to the airflowctl CLI, enabling users to get, list, clear, and update task instances directly from the terminal.

Closes: #61547
Related: #66173

Changes

airflowctl/api/operations.py

• Added TaskInstanceOperations class with get, list, clear, update methods
• Uses a _parse_task_instance_response helper to handle the different response shapes (single instance, list, or collection) from the API
• Restored PluginsOperations class that was lost during merge with main (Added plugins command to airflowctl #64935)

airflowctl/api/client.py

• Added task_instances property to the Client for auto-generated CLI command wiring
• Restored plugins property that was lost during merge with main

airflowctl/ctl/cli_config.py

• Added "clear" to output_command_list for correct CLI output handling
• Added _is_list_annotation() helper that properly unwraps Annotated[list[...] | None, Field(...)] to convert comma-separated CLI inputs into lists when the Pydantic model expects a list field
  (e.g. --task-ids t1,t2 → ["t1", "t2"])
• Excluded _parse_task_instance_response from auto-generated CLI commands

tests/airflow_ctl/api/test_operations.py

• Added TestTaskInstanceOperations with 10 unit tests covering all response shapes for get, list, clear, and update
• Restored TestPluginsOperations tests lost during merge

tests/airflow_ctl/ctl/commands/test_pool_command.py

• Moved import re to module scope

airflow-ctl-tests/tests/airflowctl_tests/test_airflowctl_commands.py

• Added end-to-end integration tests for all 4 taskinstance commands

New CLI Commands

airflowctl taskinstance list   --dag-id <dag_id> --dag-run-id <run_id>
airflowctl taskinstance get    --dag-id <dag_id> --dag-run-id <run_id> --task-id <task_id>
airflowctl taskinstance clear  --dag-id <dag_id> [--dry-run] [--only-failed] [--task-ids ...]
airflowctl taskinstance update --dag-id <dag_id> --dag-run-id <run_id> --task-id <task_id> [--new-state <state>] [--note <note>]

---

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.

[Suraj-kumar00]

Hello @potiuk,
Could you please review now and the CI Pipeline can be run?

Also could you help me get this that do i have to do the testing manually on local? This is taking so much time locally!!!

[bugraoz93]

There are some foundational things needs changing, thanks for the PR!

[bugraoz93]

I think if fields are mandatory they should be path parameter without any param name to be optional. Can you rebase? Maybe you don't have those. Because we shouldn't update old commands in this work, they should work as is and we should ensure required fields are not passed as optional for taskinstance commands too

[Suraj-kumar00]

Fixed, all required params (dag_id, dag_run_id, task_id, key, value) are now positional args in the test commands, matching how CommandFactory generates them. Rebased on main.

[bugraoz93]

Operations name shpuld be tasks as this auto generated should be same as Airlfow core cli

This creating is correct even though the static checks failing and PR not finished. Please check the operation class naming
https://github.com/apache/airflow/pull/66926/changes

[bugraoz93]

This looks bespoke to me, I don't think we should put task base exceptional bespoke implementations here. We should add them to operation side if needed, I assume we shouldn't have this much changes here