Refactor bulk TI deletion endpoint to handle map_index

[guan404ming]

Related Issue

#51564
cc @pierrejeambrun

Why

Current implementation only support task_id for bulk deletion. We need to update service to accept map_index.

How

• add BulkDeleteWithEntityAction to let BulkTaskInstanceService's deletion accept object

---

^ 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.

[bugraoz93]

Looks good! Thanks!
I have one comment. We need to keep the current behaviour and extend it as a new action. This way, anything that needs a delete with an entity can just use that action in the future and can make the code simpler without having an extra set of BulkDeleteActionWithEntity model and a single parameter can change the behaviour similar to what we are doing for Create, Update and Delete. It can be DELETE_WITH_ENTITY, for example

[bugraoz93]

Let's keep the current behaviour and add this as an extra action. This is a breaking change which makes this endpoint not backwards compatible. Maybe we can define a new action BulkAction.DELETE_WITH_ENTITY or something, and include an additional method in the service. Then we can call that method in the same route as a different action. This way, we can easily extend the bulk actions per use case and make it backward compatible

[guan404ming]

Great suggestion! I would try implement it as a new action to make it backward compatible. Thanks!