Add support for query parameters to BigQueryCheckOperator (#40556)

[aldenstpage]

BigQueryCheckOperator doesn't support query parameters. Query parameters should always be supported to discourage string-formatting, which can introduce SQL injection vulnerabilities.

The attack surface of BigQueryCheckOperator is basically non-existent. However, using query parameters everywhere is a matter of common sense and good housekeeping. A user of the module shouldn't have to choose query parameters for one operator and string formatting for the other; we should always support the safe route, which is through query parameters.

To add support, we'll imitate BigQueryExecuteQueryOperator's approach of adding a query_params argument to the constructor of BigQueryCheckOperator. An alternative approach would have been to make it possible to pass in configuration as BigQueryInsertJobOperator does, but that would have other breaking changes (like making the sql argument redundant).

Closes: #40556

[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 Contributors' Guide (https://github.com/apache/airflow/blob/main/contributing-docs/README.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

[potiuk]

A unit test is needed for that one.

[aldenstpage]

That was fast! Thanks for the speedy response.

I added a unit test (and added a missing self reference it uncovered).

[potiuk]

That was fast! Thanks for the speedy response.

You were just lucky and the change is small. Both help.

[potiuk]

Still static checks failing (I recommend to install pre-commit - it will fix things for you)

[aldenstpage]

I fixed the static check. The MySQL failure is a bit more surprising - flaky integration test / separate issue already existing in main?

[boring-cyborg]

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

[potiuk]

Yep. Was flaky it seems