Log check_query_output response via format string in Snowflake SQL API hook

[michaelneely]

Error:SnowflakeSqlApiHook.check_query_output logs the raw response dict, which violates StructuredLogMessage.event's str type.

This prevents logs from being displayed in the UI after a deferred SnowflakeSqlApiOperator finishes executing:

1 validation error for StructuredLogMessage
event
  Input should be a valid string [type=string_type, input_value={'resultSetMetaData': {'n...eatedOn': 1780320202371}, input_type=dict]
    For further information visit https://errors.pydantic.dev/2.13/v/string_type

Fix: Log the query response JSON in a templated string, matching the pattern used by other methods in the file.

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

---

Important

🛠️ Maintainer triage note for @michaelneely · by @potiuk · 2026-06-17 14:51 UTC

Helpful heads-up from the maintainers — please address before this PR can be reviewed:

• Failing test jobs: provider distributions tests / Compat 2.11.1:P3.10:, provider distributions tests / Compat 3.0.6:P3.10:, provider distributions tests / Compat 3.1.8:P3.10:, provider distributions tests / Compat 3.2.2:P3.10:. Reproduce and fix locally, then push.
• See the Pull Request quality criteria.

The ball is in your court — you've been assigned to this PR. Fix the above, then mark it Ready for review.

_{Automated triage — may be imperfect; a maintainer takes the next look.}

[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
Here are some useful points:

• Pay attention to the quality of your code (ruff, mypy and type annotations). Our prek-hooks 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

[henry3260]

Good catch

[potiuk]

LGTM — lazy %s formatting with the query id is a clear improvement over log.info(response_json), which eagerly stringified and dropped context. Test updated to match. Thanks!

---

Drafted-by: Claude Code (Opus 4.8); reviewed by @potiuk before posting

[michaelneely]

Looks like azure provider tests are failing, but that has nothing to do with this PR