Add an ability to use scan queries via new YDB operator

[vgvoleg]

Add an ability to use YDB scan queries via new YDB operator
https://ydb.tech/docs/en/concepts/scan_query

---

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

[ashb]

This makes changes to the vendored file that are not included in the upstream project https://github.com/ydb-platform/ydb-sqlalchemy/blob/main/ydb_sqlalchemy/dbapi/cursor.py -- we should submit the change there first please, or find a way to make this change that doesn't involve the vendored files diverging from the upstream project in terms of features.

[potiuk]

This makes changes to the vendored file that are not included in the upstream project https://github.com/ydb-platform/ydb-sqlalchemy/blob/main/ydb_sqlalchemy/dbapi/cursor.py -- we should submit the change there first please, or find a way to make this change that doesn't involve the vendored files diverging from the upstream project in terms of features.

Quite agree with @ashb on that one.

[vgvoleg]

This makes changes to the vendored file that are not included in the upstream project https://github.com/ydb-platform/ydb-sqlalchemy/blob/main/ydb_sqlalchemy/dbapi/cursor.py -- we should submit the change there first please, or find a way to make this change that doesn't involve the vendored files diverging from the upstream project in terms of features.

Quite agree with @ashb on that one.

These changes are already on vendor side, I've just updated the version of copied files. We still have no separate package to import directly without any issues, the problem is described here https://github.com/apache/airflow/blob/3bb6d02107493af64c4ed1b5fb4a6b8448c29945/airflow/providers/ydb/hooks/_vendor/readme.md

[potiuk]

Ah. OK then. LGTM.

[potiuk]

@ashb -> can you remove the "require changes" please?

[ashb]

I can't from my phone but please dismiss it if you can

Agreed with Ash

[boring-cyborg]

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