airflowctl: datetime.datetime-typed CLI parameters don't accept any value

### Under which category would you file this issue? Airflow Core ### Apache Airflow version airflow 3.2.2 / airflow-ctl 0.1.5 (also present on `main`) ### What happened and how to reproduce it? `airflowctl dagrun list` (and any other auto-generated CLI command with a `datetime.datetime`-typed parameter, e.g. `--start-date`/`--end-date`) rejects every possible input string. No date format — plain date, full ISO-8601, anything — will parse. **Reproduction:** ```bash airflowctl dagrun list -e <env> --start-date "2026-07-01" --limit 1 # argument --start-date: invalid datetime value: '2026-07-01' airflowctl dagrun list -e <env> --start-date "2026-07-01T00:00:00" --limit 1 # argument --start-date: invalid datetime value: '2026-07-01T00:00:00' ``` **Root cause:** In `airflow-ctl/src/airflowctl/ctl/cli_config.py`, `_python_type_from_string` builds the argparse `type=` callable for CLI arguments straight from the OpenAPI-derived operation signatures: ```python mapping: dict[str, type | Callable] = { "int": int, "float": float, "bool": bool, "str": str, "bytes": bytes, "list": list, "dict": json_dict_type, "tuple": tuple, "set": set, "datetime.datetime": datetime.datetime, "dict[str, typing.Any]": json_dict_type, } ``` For any parameter annotated `datetime.datetime`, this passes the bare `datetime.datetime` class to argparse as `type=`. argparse then calls `type(value)` on the raw CLI string, i.e. `datetime.datetime("2026-07-01")` — invoetime.datetime(year, month, day, ...)`), not a parser. Since theconstructor expects positional ints, passing a single string always raises a `TypeError`, which argparse reports as `invalid datetime value: '...'` regardless of the input. Notably, the exact same class of bug existed for `dict`-typed parxed by mapping to `json_dict_type` (a real parser using`json.loads`) instead of the bare `dict` constructor. The `datetime.datetime` entry was missed and still uses the bare type. ### What you think shou…