feat(task_instances): Add operator_name_pattern pool_pattern queue_pattern as search filter

[Pei-Cheng-Yu]

Related issues

Related: #53051

WHY

according to discussion in PR #56920
implement the search / pattern match counterpart filers in the backend for pool, queue, operator

---

^ 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 the PR! LGMT overall.

[jscheffl]

Nice to have this but "danger zone", the columns you add to be filtered is not having an index, so if this is the only part you are searching for and you have a large DB then this is triggering a full table scan and can be used as DOS as well as will have poor response time.

[jason810496]

Nice to have this but "danger zone", the columns you add to be filtered is not having an index, so if this is the only part you are searching for and you have a large DB then this is triggering a full table scan and can be used as DOS as well as will have poor response time.

Good point!
We are resolving N+1 problems recently and maybe checking whether there are indexes for all the filters will be next stage of API performance optimization.

[jason810496]

Nice!

[pierrejeambrun]

LGTM thanks

[boring-cyborg]

Awesome work, congrats on your first merged pull request! You are invited to check our Issue Tracker for additional contributions.