Refactor patch_task_instance logic

[guan404ming]

Related PR

#50443
cc @pierrejeambrun

Why

• patch_task_instance_note and _patch_task_instance_state in bulk service are very similar to what's in the route for patch_task_instance.

How

• move patch_task_instance_note and _patch_task_instance_state out of TI bulk service
• use the new service func to handle patching in the route

---

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

[jason810496]

Thanks for consolidating the common utility.

[guan404ming]

Thanks!