feat(api/endpoint): allow filtering eventlogs by attributes

[hainenber]

Closes: #34210

feat(api/endpoint): Allow filtering for Event Logs at /eventlogs endpoint using the entity's attributes.

Tests added and API schema updated

---

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

[boring-cyborg]

Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contribution Guide (https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst)
Here are some useful points:

• Pay attention to the quality of your code (ruff, mypy and type annotations). Our pre-commits will help you with that.
• In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example DAG that shows how users should use it.
• Consider using Breeze environment for testing locally, it's a heavy docker but it ships with a working Airflow and a lot of integrations.
• Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
• Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
• Be sure to read the Airflow Coding style.
• Always keep your Pull Requests rebased, otherwise your build might fail due to changes not related to your commits.
  Apache Airflow is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: dev@airflow.apache.org
  Slack: https://s.apache.org/airflow-slack

[hussein-awala]

Usually we use strictly less then before in this type of queries.

[hainenber]

Fixed in latest commit. Thanks for the review!

[hussein-awala]

We have already a dag id param:

airflow/airflow/api_connexion/openapi/v1.yaml

Lines 4797 to 4803 in 6c649ae

	DAGID:
	in: path
	name: dag_id
	schema:
	type: string
	required: true
	description: The DAG ID.

so I don't know if we should use it or create a new one, @pierrejeambrun wdyt?

[pierrejeambrun]

I think we should re-use it if this is exatly the same thing. No need to duplicate I believe

[hainenber]

Actually this dag_id parameter works for path and not as query parameter. In addition, it's set as required while eventlogs's filtering parameters aren't strictly required.

[pierrejeambrun]

In this case, maybe we can prefix that with Filter and put them in the Filter section where other filters reside in the spec. Also maybe a generic name such as FilterDAGID so we can easily reuse it. (shouldn't be specific to EventLog I believe)

[hainenber]

Parameters are now converted to filters in latest commit. Thanks!

[hussein-awala]

same for task id

[pierrejeambrun]

same

[hainenber]

Thanks for the review! I've replied in above review.

[hussein-awala]

Could you try to use different values? (ex event_1, dag_1, task_1, ...) instead of having the same value for all the variables, without that we cannot ensure that the filter is really working.

[hainenber]

Fixed in latest commit. Thanks for the review!

[hainenber]

hello there, can someone help reviewing and merge if deemed sufficient? Thanks!

[bbovenzi]

lgtm