Merge mapped and non-mapped HITL endpoints into one

[guan404ming]

Related PR

• hitl public endpoint refactoring #54697

Why

• it would be more clear to have only one endpoint to handle mapped / non-mapped hitl ti

How

• merge two endpoints into one could handle mapped / non-mapped hitl ti
• update related tests
• update frontend usage

---

^ 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 airflow-core/newsfragments.

[Lee-W]

I think we also need to update GET as well

[guan404ming]

I would update later, thanks!

[guan404ming]

Updated.🫡

[Lee-W]

I think we no longer need

airflow/airflow-core/src/airflow/api_fastapi/core_api/routes/public/hitl.py

Lines 86 to 90 in 0204a89

	ifmap_indexisNoneandtask_instance.map_index!=-1:
	raiseHTTPException(
	status_code=status.HTTP_404_NOT_FOUND,
	detail="Task instance is mapped, add the map_index value to the URL",
	)

.

some nits from backend side but mostly looks great

[jason810496]

Nice! Thanks for the PR, LGTM overall.

It would be better to place _get_task_instance, _update_hitl_detail and _get_hitl_detail common functions under service module. Non-blocking, this can be done in follow-up PR, thanks!

[Lee-W]

Nice! Thanks for the PR, LGTM overall.

It would be better to place _get_task_instance, _update_hitl_detail and _get_hitl_detail common functions under service module. Non-blocking, this can be done in follow-up PR, thanks!

let me do it in another follow up PR